Instagram Line Break Generator

Write a caption with a blank line between paragraphs, publish it, and Instagram closes the gap. The text arrives as one continuous block, the structure you wrote disappears, and nothing in the composer warns you it is about to happen. There is no setting that controls this behaviour.

The workaround creators converged on years ago is to stop sending empty lines and start sending lines that contain something. This tool does that substitution for you: it walks through your text and puts a separator line between every pair of lines, so the app has no whitespace-only line to discard.

What that separator is matters, and most pages on this subject are vague about it. Here it is a single full stop on a line of its own - visible, small, and reliable. The rest of this page is about why a visible character is usually a better trade than an invisible one.

The caption field trims. Leading whitespace, trailing whitespace, and lines that contain nothing but whitespace get collapsed before the caption is stored, which is a reasonable thing for a form to do and a frustrating one when the whitespace was load-bearing. A line containing a single space is still whitespace-only, which is why hitting the spacebar before pressing return does not help.

The behaviour is also inconsistent across entry points, and that inconsistency is what convinces people the problem is random. Pasting into the app on a phone, typing directly into the composer, and scheduling through a third-party tool do not all trim identically, so a caption that kept its spacing last week can lose it this week because you drafted it somewhere else.

The invisible-character approach - a zero-width space, or the blank braille pattern at U+2800 - exists because it fills the line without showing anything. It works often enough to be popular and fails in ways that are worse than a visible dot: some pipelines strip the character as invisible junk, some fonts render it as a replacement box, and screen readers handle it unpredictably. A full stop is a character every font has and every reader can interpret.

Read the output before you paste it. A column of full stops down the left edge of a caption looks deliberate when there are two or three of them and looks like a formatting accident when there are nine. If your draft has a break after every sentence, the fix is fewer breaks rather than a different separator.

Because the separator is visible, it is worth being intentional about where the breaks go. The strongest structure for a caption is a hook, one break, the substance, one break, the ask - three blocks and two separators. That reads as designed spacing. Converting a bulleted list where every item is its own line produces a dot between every bullet, which is when the technique starts working against you.

One more habit worth adopting: convert last, after the caption is finished. The separators make the text awkward to edit, and running the tool on an already-converted caption inserts a second round of dots between the first round.

Your text is split on every newline into an array of lines, and those lines are rejoined with a newline, a full stop, and another newline between each pair. A three-line input becomes a five-line output; an n-line input becomes 2n − 1 lines. Nothing else about the text is touched - no trimming, no normalising, no character substitution.

The consequence of joining rather than filling is that separators land between lines, not on blank lines you already wrote. If your draft already has a blank line between paragraphs, that blank line is itself one of the lines being joined, so it receives a dot on either side. Drafting with single newlines between paragraphs and letting the tool create the spacing gives a cleaner result than drafting with double newlines.

The whole operation is a string split and join running in your browser as you type. There is no request, no queue, and no preview step - the output field is the finished caption, and the copy button puts exactly those characters on your clipboard.