Copy a character
Tap any character above. Braille blank (U+2800) is the safer default — it renders consistently across the LinkedIn feed, mobile app, and search.
Platform guide
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.
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.
Tap any character above. Braille blank (U+2800) is the safer default — it renders consistently across the LinkedIn feed, mobile app, and search.
Paste into a post, your headline, the about section, a comment, or your name. Avoid the URL and skills fields, which strip non-standard characters.
Long-press the field, choose Paste, then publish or save. The text disappears from view, but LinkedIn still counts it as content and the field passes the empty check.
LinkedIn blocks truly empty comments. A single invisible character passes the check and posts as a blank line in the thread, with your name next to it.
The 3,000-character post has no paragraph-break button in every editor. Invisible characters give you a manual blank line — but only the first ~210 characters show before See more.
Paste a zero-width character into the name field and your profile shows a blank tag in comment threads. Your profile URL is unaffected.
The 220-character headline accepts Unicode. Invisible characters let you nudge spacing, though only about 60–70 characters show in search results.
Post a comment that looks empty. Stays well inside the 1,250-character cap — you only need one invisible character.
Add blank lines or push a hook down in the 3,000-character post. Each invisible character counts against that total.
Make your displayed name appear blank in threads. The profile URL keeps its original slug.
The 2,600-character about section accepts invisible Unicode for manual line breaks, with roughly the first 300 visible before See more.
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.
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.
Yes, but not an empty one. LinkedIn blocks truly empty comments. Paste one invisible character and submit — the comment posts as a blank line in the thread, with your name next to it.
LinkedIn counts UTF-16 code units, not visible glyphs. Bold and italic Unicode letters (the ones formatting tools paste) are surrogate pairs, so each one counts as two. An 80-character bold line quietly eats 160 of your 3,000-character post budget.
Yes. The name fields accept Unicode, which is why you occasionally see blank names in comment threads. Your profile URL keeps its original slug and is unaffected.
Braille blank (U+2800) renders consistently across the feed, mobile app, and search, based on reports from users who paste them regularly. Zero-width space (U+200B) works too, but occasionally shows a hairline gap on mobile.
Two common causes. Search truncates the 220-character headline around 60–70 characters on mobile, so invisible characters past that point never render there. Or an app update changed which characters the renderer accepts. Re-paste braille blank (U+2800) near the start.
Invisible characters are standard Unicode and aren't called out in LinkedIn's user agreement. That said, using them to evade filters, inflate engagement, or impersonate other members can still get your content removed or your account restricted. Use them for formatting, not for abuse.
Pick braille blank if you're not sure, paste it into a comment or your headline, and see how LinkedIn renders it on your device.
Copy a characterExplore invisible text generators for other platforms