How to Show Not Tell in Fiction That Truly Resonates
Learn how to show not tell in fiction with practical revision techniques, real novel examples, and a scene-level checklist for stronger, more immersive prose.
You know the paragraph. The one that says your character is devastated, the hallway is cold, and the night feels lonely, but nothing in it moves. On the page, it reads like a report. In your head, you can hear what it should be doing, but the sentence keeps refusing to become a scene. That is usually the moment a novelist reaches for how to show not tell, and usually the moment the phrase gets misunderstood.
Table of Contents
- Why Show Not Tell Is a Revision Tool, Not a Rule
- Four Diagnostic Signals That Tell You a Line Is Telling
- The Camera Test and the Trigger to Action Chain
- Four Micro Lessons for Dramatizing Any Scene
- When Telling Is the Better Choice
- Your Scene-Level Checklist and How Story Intelligence Helps
Why Show Not Tell Is a Revision Tool, Not a Rule
A flat draft often starts with a sentence like, “She was furious.” Nothing is technically wrong with it, but it lands like a label stuck on a file folder. If you want the reader to feel the fury, you need evidence, not a verdict. That is the useful idea behind how to show not tell, and it works best when you treat it as a revision choice, not a commandment.
What the craft advice is actually doing
Writing guides for fiction keep circling the same distinction, showing puts the human subject, action, and sensory detail in the room, while telling compresses information into summary. Modern craft advice tends to treat that difference as a diagnostic tool. Draft first, then return and ask where exposition is carrying too much emotional load, where a scene should be dramatized, and where summary is doing its job cleanly. That shift matters because not every line needs to perform at the same intensity.
A novel works when the writer decides what deserves the reader's full attention. High-emotion moments, reversals, confrontations, and revelations usually deserve dramatization. Transitions, setup, and routine movement often don't. That is the working principle I trust on the page, dramatize the moments that carry emotion or meaning, summarize the rest.
Practical rule: if a passage matters because of what it makes the reader feel, show it. If it matters because it moves the story forward, summarize it unless the moment itself carries tension.
Why the difference changes the reading experience
Readers infer character through action. They infer tension through response. They infer subtext through contradiction. When a page tells them what to think, it closes that interpretive space. When it shows a gesture, a beat, or a reaction, it hands them the work of meaning-making, and that usually feels more alive.
Take Jane Austen's social scenes. She rarely has to announce that a person is vain, awkward, or calculating. A remark, a pause, a look at the wrong moment, does the job. The reader sees the pressure in the exchange and draws the conclusion. That's not decorative writing. It's controlled inference.
This is why the old slogan gets in trouble when it becomes absolutist. A manuscript bloated with summary feels flat, but a manuscript that dramatizes every bridge between scenes can feel overbuilt and slow. Revision is where you separate the moments that need pressure from the ones that just need to get you to the next meaningful beat. If you keep that distinction clear, how to show not tell stops being a vague writing mood and becomes a usable editorial standard.
Four Diagnostic Signals That Tell You a Line Is Telling
If a draft feels mushy, the problem is often mechanical before it is artistic. A line can be telling because it names emotion directly, leans on static description, hides behind internal verbs, or filters experience through a needless layer. Train your eye to spot those signals and revision gets much easier.
Emotion labels and state-of-being verbs
The first signal is the obvious one, a sentence that names the feeling. “He was sad.” “She was angry.” “They were excited.” Those lines are not illegal, but they are usually placeholders. They tell the reader the conclusion without giving the body, voice, or environment enough room to carry the meaning.
State-of-being verbs often sit right beside those labels. “Was,” “were,” “is,” and “are” aren't always a problem, but when they hold the whole sentence in place, the prose tends to go static. Compare a sentence like, “The room was tense,” with a more scene-based line from a novel such as The Handmaid's Tale, where atmosphere comes through remembered sensory detail and the present scene's emotional pressure rather than a label. The effect is different because the reader has to assemble the tension instead of being handed it.
Mental-state verbs and filter words
The next two signals are more subtle. Mental-state verbs such as “thought,” “knew,” “realized,” “felt,” and “noticed” often compress a full scene into a summary of cognition. Filter words like “saw,” “heard,” and “watched” create another layer between reader and event. They're not forbidden, but overuse can make the prose feel like a witness statement instead of lived experience.
Try this with a simple example. “She realized the door was open” becomes more immediate when the line moves into observable behavior, perhaps with a pause, a step back, or a sudden check over the shoulder. The famous opening movements of Charlotte's Web work partly because the dialogue and reaction reveal Fern's alarm without stopping to explain her emotional state. The scene gives the evidence, then lets the reader do the interpreting.
Read a paragraph once for story, then again for those four tells. If you can circle three or four of them in a single sentence, the line probably needs revision.
The point is not to outlaw these forms. It is to notice when they're doing lazy labor. A manuscript full of labels, summaries, and filters keeps the reader at arm's length. A manuscript that swaps those signals for concrete action starts to feel embodied. That's the mechanical side of how to show not tell, and once you can spot the signals, you stop arguing with the page and start editing it.
The Camera Test and the Trigger to Action Chain
The fastest way I know to decide whether a line belongs in scene or summary is to ask a blunt question, can a camera see this? If the answer is no, you may be looking at interpretation rather than dramatized action. That doesn't make the line bad, but it does tell you what kind of work it's doing.
Camera visible versus camera invisible
“She felt ashamed” fails the test because the shame is internal and unnamed. “She looked down, folded her arms, and answered too quickly” passes because the reader can observe the behavior and infer the feeling. ProWritingAid's version of the camera test is useful because it strips away mystique. It doesn't ask whether the line sounds literary. It asks whether the page contains observable evidence.
This matters most in revision. First drafts often need summary to keep momentum. Revision is where you decide which internal states deserve dramatization and which can stay as efficient explanation. If a sentence is camera-invisible but necessary, keep it as summary. If it's camera-invisible and emotionally central, it probably needs work.
The trigger to action chain in practice
A stronger pattern for interior life is the trigger → visceral response → thought → decision → outward action chain. It keeps emotion in motion. Instead of telling the reader a character is anxious, give the thing that starts the reaction, then the body's response, then the thought that follows, then the choice that lands on the page.
Imagine a phone call that brings bad news. The trigger is the ringtone. The visceral response might be a dry mouth or a stomach drop. The thought could be a single hard sentence the character won't admit aloud. The decision is whether to answer. The outward action is the hand moving toward the phone or away from it. That sequence creates scene-level evidence instead of summary.
The same logic applies when you want to deepen sensory presence. In high-stakes moments, two non-visual senses are usually enough. A snapped tone in a voice, the smell of bleach, the rough drag of wool at the wrist, the temperature of a metal handle. If you overload all five senses at once, the prose gets muddy. If you choose one or two precise details, the reader can build the rest.
A good scene often gives the reader one visible action and one physical sensation, then trusts the imagination to do the rest.
The how to show not tell method ceases to be a slogan and becomes a repeatable process. Check the camera test. Follow the chain. Keep the sensory evidence lean. That combination does more useful work than a pile of abstract feeling words ever will.
Four Micro Lessons for Dramatizing Any Scene
The shortest path to better pages is usually not “write more vividly.” It's fix the weak mechanism. Most flat scenes fail in one of four places, sensory detail, action, dialogue, or stakes. If you can repair those, you often don't need to touch much else.
Sensory detail and action
A generic line sounds like this, “He was nervous.” A better line lets the body and setting carry the feeling. In The Road, Cormac McCarthy's stripped description often does this work by letting environment, hunger, and silence shape the mood instead of naming it outright. The reader feels the tension because the world itself is pressuring the characters.
For your own draft, don't pile on description for its own sake. Use one concrete sensory fact that matters in the moment. A sticky glass. A fluorescent hum. The metallic taste after a bad argument. Then connect it to a purposeful action, because action keeps the scene from turning into wallpaper.
Two-minute exercise: write a moment of guilt without using the word guilt or any synonym. Give the character one object to handle and one physical sensation to notice.
Dialogue and subtext
Dialogue gets lazy when a character says exactly what they feel. “I'm angry.” “I'm hurt.” “I'm jealous.” Real scenes usually work harder when the spoken line and the hidden feeling are out of sync. A character can say, “Fine,” while packing a bag. Another can offer a polite question while refusing eye contact. The reader gets the contradiction, and contradiction creates tension.
Reedsy's advice on dialogue is solid here, read the line out loud, trim the over-explained speech, and let silence carry part of the exchange. Raymond Carver built whole rooms of unease out of what characters refused to say directly. The same principle works in novels. The line is rarely just the line.
Stakes that earn the scene
A scene does not feel alive because it contains action. It feels alive because the action can change something. If nothing can be lost, delayed, exposed, or damaged, the writing may be polished and still feel weightless. That's why the question is not only what the character does, but what happens if they do it wrong.
Use stakes as the final pass on any scene. Ask what the character wants in that moment, and what stands in the way. If the answer is vague, the prose will probably wobble too. How to show not tell is strongest when the visible action and the consequence are tied together.
Two-minute exercise: take a bland exchange from your draft and rewrite it so one line of dialogue risks something concrete, even if it's only embarrassment, a lie being exposed, or a door closing.
The page gets stronger when each beat changes pressure, not when every sentence tries to sound rich.
For a deeper structural pass, I like to think of scene work in terms of momentum and consequence, which is the same problem a solid scene breakdown approach helps you notice from a wider angle. The craft move is still yours. The tool just makes the weak spots easier to see.
That's the part many writers skip. They try to make every line more vivid instead of making the scene more causally clear. Once the reader can feel the action, hear the subtext, and understand the consequence, the prose starts doing its real job.
When Telling Is the Better Choice
The hardest lesson in how to show not tell is that sometimes telling is the cleaner professional move. Not every sentence should be dramatized. Some information is low-emotion, transitional, or already obvious, and forcing it into a scene can make the draft heavier, not better.
Where summary earns its keep
Backstory usually benefits from compression. So do time jumps, routine travel, and setup that would stall the chapter if you acted it out in full. If a character moved across town, ate a sandwich, and thought about last winter for three paragraphs, you may have a pacing problem rather than a richness problem. Summary can clear that rubble fast.
Helping Writers Become Authors makes the useful point that the question is often whether the information is already evident from context and whether the reader needs it explained at all. That's the judgment call. If the answer is yes, tell it. If the answer is no, dramatize it. Professional fiction depends on that kind of discrimination.
The ratio question
I don't treat ratios as math, but they're a useful feel for revision. In essential emotional scenes, a strong working balance is about 80% showing / 20% telling. In action-heavy scenes, the balance often shifts closer to 90% / 10%. In transitions, something closer to 50/50 can be perfectly right because the job is movement, not immersion.
Those ratios help because they keep you from swinging to one extreme. A writer who fears exposition can overwrite every hallway, every breakfast, every hand reaching for a coat. A writer who fears dramatization can flatten the whole book into summary. The page usually improves when you let each mode do the kind of work it does best.
Practical rule: if the scene's purpose is emotional, lean on dramatization. If the scene's purpose is logistics, time, or setup, keep the telling concise and clean.
That is why a novel like Pride and Prejudice can move briskly through social logistics and then slow down when a conversation shifts a relationship. The rhythm changes because the narrative value changes. That's not inconsistency. It's control.
If pacing is where your draft starts to sag, a separate look at pacing choices can help you decide whether the problem is too much summary, too much scene, or just the wrong balance in a chapter. The answer is rarely “remove all telling.” It's usually “move it to the right place.”
Your Scene-Level Checklist and How Story Intelligence Helps
When I revise a scene, I run the same small checklist every time. It keeps me honest. It also stops me from polishing a line that should've been cut back to summary in the first place.
A simple checklist for revision
- Run the camera test. If a camera couldn't see it, decide whether it needs to be a scene or a summary.
- Scan for diagnostic signals. Look for emotion labels, state-of-being verbs, mental-state verbs, and abstract nouns.
- Walk the trigger to action chain. Make sure reaction has a cause, then a body response, then a choice.
- Mix two senses. Add at least two non-visual details where the scene carries emotion or risk.
- Choose your ratio. Decide how much showing and telling the moment needs.
That's enough to catch most weak passages without turning revision into superstition. The point is not to make every paragraph highly dramatized. The point is to make every passage do its own job cleanly.
For writers who want a second set of eyes on the whole manuscript, Arbento reads the writer's whole manuscript and gives story intelligence through beat analysis, Codex continuity tracking, scene feedback, and writing signals like tone, readability, and pacing. I'd treat that as diagnostic support, not a replacement for judgment. It's useful when you want to spot where a chapter is leaning too hard on exposition or where continuity and pacing are blurring the effect of a scene.
If you're also thinking about readability, a closer look at readability checks pairs well with this kind of revision, because clear prose and dramatized prose usually help each other. The craft question stays the same. What belongs on the page as action, and what belongs as summary?
If you want a manuscript-level read on where your scenes are showing too little or overexplaining too much, visit Arbento. It reads your whole book, not just isolated lines, so you can see where pace, continuity, and scene logic are slipping. Then you can revise the story you actually wrote, with cleaner judgment and fewer blind spots.