Likes are cheap and saves are the signal that matters. A caption someone saves is a caption they intend to come back to, which usually means it taught something or listed something. All seven structures below are built around that: give the reason to save inside the first two lines, not after the third paragraph.
What every structure has in common
- The hook is a claim, not a greeting. "New drop" is a greeting. "Four ways to do X without Y" is a claim.
- Line breaks every one or two sentences. A wall of text is scrolled past regardless of what it says.
- The ask is specific and late. "Save this for your next launch" beats "follow for more".
- One caption, one idea. Two ideas in one caption means neither is remembered.
1. The number list
1. [SHORT, SPECIFIC]
2. [SHORT, SPECIFIC]
3. [SHORT, SPECIFIC]
[ONE LINE: who this is for and when they will need it.]
Save this for [the moment it becomes useful].
Cut this line: the closing "what do you think?" — it asks for a comment nobody has a reason to write.
2. The mistake
Here is what actually happens: [ONE OR TWO SENTENCES, PLAIN].
Do this instead: [THE FIX, ONE STEP].
I did this wrong for [TIME PERIOD] before [WHAT CHANGED].
Cut this line: any version of "we have all been there". It pads and it says nothing.
3. The before and after
After: [CONCRETE STATE].
The only thing that changed: [ONE CHANGE].
[ONE HONEST LINE ABOUT WHAT DID NOT IMPROVE.]
Cut this line: the superlative. If the after state needs an adjective to sound good, the numbers were not specific enough.
4. The process
Step 1: [VERB, OBJECT, TIME IF KNOWN]
Step 2: [VERB, OBJECT]
Step 3: [VERB, OBJECT]
The step people skip: [WHICH ONE, AND WHAT IT COSTS].
Cut this line: "it is easier than you think". If it were, the post would not be needed.
5. The quiet announcement
It does [ONE THING]. It does not do [THE THING PEOPLE WILL ASSUME].
[WHO IT IS FOR, IN ONE LINE].
[WHERE TO FIND IT, PLAINLY].
Cut this line: "we are excited to announce". Three words of nothing at the top of the only three lines people see before tapping more.
6. The behind-the-scenes
Here is the part nobody posts: [ONE CONCRETE DETAIL].
[ONE SENTENCE ON WHY IT MATTERED, OR WHY IT DID NOT.]
Cut this line: the journey metaphor. "It has been quite the journey" appears in almost every generated version of this post.
7. The question that answers itself
Short answer: [ONE SENTENCE].
Longer answer, because the short one is wrong sometimes: [TWO OR THREE SENTENCES WITH THE CONDITION].
Save this — the condition is the part people forget.
Cut this line: "drop your questions below" when you have already answered the only question the post raises.
Why generated captions get scrolled
A model writes a competent caption in the register of a brand, not of a person. The result is grammatical, complete, and has no reason for anyone to stop. The fix is not a better prompt; it is supplying the one thing only you have — the number, the attempt count, the thing that did not work. Every structure above has a slot for exactly that, and the caption only works when that slot is filled with something real.
Generate the structure, supply the detail
Seven shapes are enough for a month of posts if every one carries one real number.
Try Rytr →Frequently Asked Questions
Do caption templates hurt engagement?
The structure does not; the filler does. A template gives you the order of the lines, and the specific detail you put in the bracket is what makes it worth saving.
What should the first line do?
Make a claim rather than a greeting. "Four ways to do X without Y" gives a reason to read; "new drop" does not.
Why optimise for saves instead of likes?
A save means the reader intends to return to it, which happens when the post teaches or lists something. Likes cost the reader nothing and signal less.
How many hashtags should a caption have?
Fewer than most guides suggest, and placed after the ask rather than inside the hook. The hook is the only part most readers see.