LinkedIn Invisible Text Generator
Copy zero-width and braille blank characters for LinkedIn posts, headlines, the about section, and comments. Each one is tested against LinkedIn's actual limits — including the 220-character headline cap and the UTF-16 counting quirk.
Zero Width Space
U+200B
Generated invisible text
3 charactersTest Area
What invisible text actually does on LinkedIn
LinkedIn treats zero-width and braille blank characters as real characters. They pass the empty-field check in posts and profile fields, but they also count against your limit — and on LinkedIn that limit is counted in UTF-16 code units, which changes the math. The headline gets 220 characters (only about 60–70 show in search), the about section 2,600, posts 3,000, and comments 1,250. The first and last name fields accept Unicode, as does the headline, which is why you occasionally see a blank name in comment threads. Drop a few invisible characters into a 3,000-character post and you've spent almost nothing; stack them in a 220-character headline and the budget tightens fast. This page gives you the same characters we tested in each LinkedIn field, so you can paste without guessing which one renders and which one gets stripped.
How to paste invisible text into LinkedIn
What invisible text is actually useful for on LinkedIn
Where on LinkedIn you can use it
Field-by-field behavior on LinkedIn
LinkedIn counts characters with JavaScript's string.length, which is UTF-16 code units — not visible glyphs. That matters here more than on most platforms. Zero-width characters (U+200B, U+2800) live in the Basic Multilingual Plane and cost one unit each. But the bold and italic Unicode letters that formatting tools paste (the mathematical alphanumeric symbols above U+FFFF) are surrogate pairs, so each one costs two units. An 80-character bold headline quietly eats 160 of your 220. The headline (220), about section (2,600), posts (3,000), comments (1,250), connection note (200 free / 300 Premium), and the name fields all accept invisible Unicode. InMail is the quieter exception cluster: the subject line caps at 200 and the body at roughly 1,900, and both count the same UTF-16 way.
Practical notes before you paste
Braille blank (U+2800) renders consistently across the LinkedIn feed, mobile app, and search.
LinkedIn counts UTF-16 code units. Invisible characters cost one unit; bold/italic Unicode letters cost two.
Only the first ~210 characters of a post show before See more. Don't bury your hook behind invisible line breaks.
The headline is 220 characters, but search truncates it around 60–70 on mobile. Front-load the meaningful part.
Connection notes cap at 200 characters on free accounts and 300 on Premium — invisible characters waste that budget fast.
Don't put invisible characters in the profile URL or skills fields. They get stripped and can break the field.
Accessibility tools sometimes misread Unicode-formatted text. Use invisible and styled characters sparingly in job-critical copy.
The feed, mobile app, and search results render zero-width characters slightly differently. Check the surface your readers use.
Common questions about invisible text on LinkedIn
LinkedIn compatibility, by field
Posts (3,000 characters), the headline (220), the about section (2,600), comments (1,250), connection notes (200 free / 300 Premium), and the name fields all accept invisible Unicode characters. LinkedIn counts characters as UTF-16 code units, so zero-width characters (U+200B, U+2800) cost one unit each, while bold and italic Unicode letters cost two units because they're surrogate pairs. The profile URL and the skills fields strip non-standard characters. Rendering is consistent across the desktop feed, the mobile app, and search results for braille blank (U+2800); zero-width space (U+200B) occasionally shows as a hairline gap in the mobile comment view. The See more cutoff lands at roughly 210 characters in the feed.
Other Invisible Text Tools
Explore invisible text generators for other platforms
