Writing October 3, 2026

What is foreshadowing?

The best twists produce two reactions at once: I did not see that coming, and of course. The second one is foreshadowing doing its job.

Foreshadowing is information a story gives you early that only makes sense later. It is the reason a good twist produces two reactions at once — I did not see that coming, and, half a second later, of course. Without it, a surprise is just a surprise, and surprises on their own feel cheap.

Foreshadowing is not a hint to the reader. It is a receipt you can show them afterwards.

What it is actually for

Readers forgive almost anything except being cheated. When something enormous happens with no groundwork, the reaction is not awe, it is suspicion: the author made that up on page 300 because they needed it. Foreshadowing is how you prove you did not. It converts unexpected into inevitable in hindsight, which is the only kind of unexpected that satisfies.

Note the timing. Foreshadowing does almost no work on the first read, by design. It pays out in the last twenty pages and again, properly, on a reread — one of several reasons a second pass through a good book is a different book, which we argue in why rereading is worth it.

The three kinds

Direct. The story tells you flatly that something is coming. A prologue from the aftermath, a narrator saying it was the last time they saw the house standing, a prophecy. The tension stops being what and becomes how, which is a trade, not a loss.

Planted. A concrete detail introduced casually and used later: a key, a scar, a debt, a habit. This is the workhorse, and it has a famous rule attached — if you show a loaded gun in act one, it should go off by act three. The point of that rule is less about guns than about economy: a detail given weight must eventually carry some.

Atmospheric. Weather, imagery, a recurring motif, somebody being a little too cheerful. It does not predict an event, it prepares a mood, so the reader is braced before they know what for. Done badly it is just gloom. Done well it is unbearable.

Foreshadowing, clues and red herrings

These get mixed up constantly. A clue is addressed to the reader and asks to be solved; the reader is meant to be working. Foreshadowing is addressed to the reader in retrospect; they are not supposed to be working at all. And a red herring is a clue built to point the wrong way — a deliberate misdirection, which only plays fair if the real foreshadowing was there alongside it.

The distinction matters because the techniques are different. Clue-laying is a fairness problem with its own mechanics, which we handle in how to plant clues in a mystery. Foreshadowing is a weighting problem: how much emphasis can you give a detail before the reader notices you giving it?

How to plant one without giving it away

Give it another job. The detail should be doing something in the present scene — characterising somebody, making a joke, getting a door open. A thing that exists only to matter later announces itself.

Put it where attention is not. Mid-paragraph, mid-conversation, under something louder. The end of a scene is the worst place; readers remember endings.

Mention it more than once, unevenly. Once is forgettable, three times evenly spaced is a drumbeat. Twice, with a long gap and different emphasis, is about right.

Underplay it. New writers plant too hard — italics, a pointed line of dialogue, a character wondering aloud why that was strange. Trust the reader to carry the detail without being asked to.

How much is enough

The honest answer: less than you think, and you cannot judge it yourself. You know the ending, so every plant looks blindingly obvious to you and invisible to everybody else. This is the single thing you need a reader for — not did you like it but did you see it coming, and did it feel earned. Two readers and you have your answer; it is one of the few questions where feedback is genuinely diagnostic, and we go through how to ask for it in how to get feedback on your writing.

If the answer is that they saw it coming a hundred pages out, cut a plant rather than adding a twist. If it came out of nowhere, do not explain more at the end — go back and add one quiet detail in the first third. Fixes to foreshadowing nearly always belong at the start, not the finish, which is also why endings so rarely get fixed by rewriting the ending: see how to write a satisfying ending.

Reading for it

You can enjoy this from the other side too. Once you know the shape of the trick, half the pleasure of a well-built book is watching the author set things up in plain sight. We build Arwy, an Android app that connects you with other people reading the same book, and the single most common message after a reveal is some version of go back and read chapter four. That is foreshadowing getting the applause it waited the whole book for.


Writing something with a twist in it? Arwy is on Google Play.

Writing something yourself? Everything we know about publishing it — free guides, how rights work, and what you can actually earn — is collected on Arwy for writers.

← All posts