Generate short post spacers for longer public text composers where visible context and published rendering matter.
Recommended:Use No-Break Space for compact post gaps, Em Space for wider section breaks, and Hangul Filler for blank-looking separators between visible sections.
Safety note:Post composers may trim or normalize invisible characters. Use this for formatting and compatibility testing, not misleading or disruptive posts.
Controls
Allowed range: 1 to 60. Short samples are easier to verify across apps.
Leave blank for a simple sample, or type a short reference. Maximum 120 characters.
Output and diagnostics
Selected: NoneCode points: Not generatedUnits: 0Width/type: Not testedVisible chars: 0
Choose a preset, generate or analyze, then copy or transfer to the Test Box.
Hangul Filler
U+3164
AㅤB
Blank-looking special character
No-Break Space
U+00A0
A B
Visible spacing character
Zero Width Space
U+200B
AB
Zero-width or format character
Em Space
U+2003
A B
Visible spacing character
Test Box
Characters: 0—
FAQ
What is invisible text for posts used for?
It is used for layout checks, line gaps, or blank-looking separators in longer post composers.
How is this different from caption text?
Posts usually allow longer text and more context; captions are shorter media-adjacent fields.
Why does spacing change after publishing?
The platform may normalize the post after save, so published view can differ from editor view.
Which character is best for post layout?
No-Break Space works for compact gaps, Em Space for wider gaps, and Hangul Filler for blank-looking separators.
When should I use post text instead of caption text?
Use post text for full post layout, paragraphs, links, mentions, and feed rendering. Use caption text for caption-specific line spacing and saved caption behavior.
Why does my post spacing look different after publishing?
Draft and published feed views can compress whitespace differently. Test a short draft and compare the published layout.