No-Break Space looks exactly like a regular space but does two things the regular space cannot: it refuses to let a line break at that point, and it does not collapse in HTML. That combination makes it the workhorse of careful typography.
Click the button above to copy No-Break Space, then paste it wherever you need it. Nothing will appear on your clipboard preview - that is expected, because the character is blank.
| Unicode code point | U+00A0 |
|---|---|
| Character name | No-Break Space |
| Unicode category | Zs (Space Separator) |
| Rendered width | Same width as a regular space in the current font |
| Line breaking | Non-breaking - a line will never wrap here |
| Collapses in HTML | No |
| Survives trim() | Usually yes |
| HTML entity | |
| JavaScript escape | '\u00A0' |
| CSS escape | \00A0 |
Need these values in another format? The HTML space characters converter turns any Unicode whitespace character into HTML entities, JavaScript escapes and CSS escapes.
U+00A0 NO-BREAK SPACE, usually written as NBSP or in HTML, renders at the same width as the font's regular space. The difference is behavioural. Line-breaking algorithms treat it as glue that cannot be broken, so the words on either side of it are guaranteed to stay on the same line.
Because NBSP is not ASCII whitespace, HTML does not collapse runs of it. Ten NBSP characters in a row produce ten spaces of visible indentation, which is why it became the classic way to force spacing in web pages and email templates long before CSS made that unnecessary.
The same character can be preserved in one place and silently removed in another. Here is what actually happens to No-Break Space in the three contexts that matter most.
Does not collapse. Each NBSP renders as its own space, which makes it the traditional way to indent without CSS.
Often survives. Many validators only strip ASCII whitespace, so an NBSP-only value can pass a required-field check - though stricter validators normalise it to a regular space first.
Widely preserved, and it is the most reliable fallback when Hangul Filler is rejected. Some platforms normalise it back to a regular space and then trim it, so test before relying on it.
Not sure what is in a string you already have? Paste it into the invisible character detector to see every hidden character with its code point, or use remove invisible characters to strip them out.
Typography and HTML, where you want spacing that holds its position and never breaks across a line. It is also the best second choice for blank text when Hangul Filler does not work.
If what you actually need is text that looks completely empty - a blank WhatsApp message, an empty Instagram highlight name, a blank comment or a Free Fire name space - then Hangul Filler is the character to use, because it is not classified as whitespace and survives the trimming that removes No-Break Space.
Different apps prefer different Unicode characters. Start with these combinations.
Best first choice: Hangul Filler (U+3164). Alternatives: Zero Width Space and No-Break Space.
Best first choice: Hangul Filler. Alternative for tighter formatting: Zero Width Space.
Start with Hangul Filler. If the game rejects it, try Space or No-Break Space.
Use No-Break Space for preventing line breaks, EN Space and EM Space for wider spacing, and Thin Space or Hair Space for finer adjustments. For code-ready values and conversion, see HTML Space Characters.
Width is the fastest way to choose between these characters. If No-Break Space is not right for your use case, one of these probably is.
| Character | Unicode | Width |
|---|---|---|
| Zero Width Space | U+200B | Zero - it occupies no horizontal space at all |
| EN Space | U+2002 | Exactly 1/2 em - half the current font size |
| EM Space | U+2003 | Exactly 1 em - equal to the current font size |
| Three-Per-Em Space | U+2004 | Exactly 1/3 em |
| Four-Per-Em Space | U+2005 | Exactly 1/4 em |
| Six-Per-Em Space | U+2006 | Exactly 1/6 em |
| Figure Space | U+2007 | Exactly the width of a digit in the current font |
| Punctuation Space | U+2008 | Exactly the width of a period in the current font |
| Thin Space | U+2009 | About 1/5 em, though the exact width is left to the font |
| Hair Space | U+200A | The narrowest visible space - typically about 1/10 em or less |
See all 18 Unicode space and invisible characters compared →
They look identical. The differences are that a line can never break at an NBSP, and that consecutive NBSP characters do not collapse in HTML while consecutive regular spaces do.
Yes. is the HTML named entity for the character U+00A0, and is the numeric form. All three produce the same character.
Often, yes. NBSP passes more validators than a regular space because many of them only strip ASCII whitespace. It is less reliable than Hangul Filler, which is not classified as whitespace at all, so try NBSP as a fallback.
Explore the most useful guides on BlankText.Net for blank messages, Instagram, gaming nicknames, and Unicode spaces.