The nbsp in HTML is a non-breaking space character entity that prevents line breaks between words. It renders as a visible space but ensures adjacent text stays together on the same line.
When a web browser encounters a regular space in HTML, it collapses multiple spaces into one and allows line breaks at word boundaries. The entity overrides this behavior. It's equivalent to U+00A0 in Unicode and appears as a standard space in rendered text, but it blocks automatic line wrapping.
For example, in the phrase "100 km/h", the "100" and "km/h" stay together on the same line. Without , the browser might split "100" from "km/h" at the end of a line, which can confuse readers.
HTML treats plain text spaces as flexible whitespace. Multiple spaces collapse into one, and line breaks can occur at any space. The entity changes this behavior by inserting a fixed-width space that resists breaking.
Browsers interpret as a single character with a width equal to a normal space. Unlike regular spaces, it doesn't trigger line breaks unless explicitly forced by CSS or a hard line break (<br>).
When rendering, the browser calculates line positions based on character widths. Since is a non-breaking space, the line-breaking algorithm skips it as a potential break point. This maintains visual continuity for specific word pairs.
Use when you need consistent spacing that won't be disrupted by responsive layouts or changing text resizing. Common cases include:
Another frequent use is in date formats: "June 2024" keeps the month and year together. Without , a narrow screen might break "June" from "2024".
Accessibility tools rely on correct spacing. Screen readers may misinterpret word boundaries if spaces are collapsed or missing. Using helps punctuation and spacing reflect intended meaning.
Developers often misuse when they should use CSS. For example, using to align elements horizontally is incorrect. Instead, use margin, padding, or flexbox.
A common error is overusing to create large gaps. This harms readability and accessibility. Use CSS properties like margin or padding for spacing between elements. should be reserved for fine-grained control within text.
Some assume is the same as a regular space. It's not. While both appear visually identical, is a distinct character with different line-breaking behavior. In code, is represented as - not just a space character.
Also, avoid using in place of <pre> or <code> for preserving whitespace in code blocks. These elements preserve formatting by default. Using inside them adds unnecessary complexity.
There are several variants of non-breaking space in Unicode and HTML. The most common is , but others exist for specific purposes:
| Entity | Unicode | Description | Use Case |
|---|---|---|---|
| | U+00A0 | Standard non-breaking space | Most common use: prevent line breaks between words |
|   | U+2002 | En space (half em) | Spacing between columns or in typography |
|   | U+2003 | Em space (full em) | Large spacing, often in legal or formal documents |
|   | U+2009 | Thin space | Between letters in abbreviations: "i.e. e.g." |
Use for basic non-breaking spacing. Use or only when precise typographic control is needed. Avoid unless working with international typography standards.
For example, in a legal document, "Section 3.1" uses to keep the section number with the label. But "Chapter 2 - Introduction" uses between "Chapter 2" and the em dash, while separates the dash from the text for better visual balance.
Consider this HTML snippet:
<p>123 Oak Street, Apt 4B</p>
On a mobile device, this may render as:
123 Oak Street, A
pt 4B
The word "Apt" splits across lines. To fix this, insert between "Apt" and "4B":
<p>123 Oak Street, Apt 4B</p>
Now the text displays as:
123 Oak Street, Apt 4B
This ensures the apartment number remains readable and avoids confusion. The prevents the line break without affecting visual appearance.
I encountered this issue while building a property listing site. Users reported difficulty identifying apartment numbers due to broken formatting. Adding resolved the problem across all screen sizes.
Many tutorials incorrectly claim that is "invisible" or "doesn't take space." That's false. takes up the same horizontal space as a regular space. It's not invisible-it's just unbreakable.
Another myth: is required for multilingual sites. Not true. Unicode handles spacing correctly across languages. Use only when you need to enforce a break-free boundary. Overuse can harm internationalization.
According to the W3C HTML specification, is valid in text content and should be used sparingly. The MDN Web Docs clarify that "non-breaking spaces are useful for keeping related words together, but should not replace proper layout techniques."
Avoid using in form labels or buttons where changing content changes size. CSS-based solutions like white-space: nowrap are more maintainable and accessible.
Use only when you need to prevent a line break between two words. For larger spacing, use CSS. For layout, use Flexbox or Grid. For responsive design, use relative units like em or rem.
Always test your HTML with a screen reader. Tools like axe or Lighthouse flag improper use of in contexts where it disrupts navigation. Ensure that spacing doesn't interfere with keyboard focus or reading flow.
Finally, validate your HTML with the W3C validator. It flags invalid or redundant use of . Keep your markup clean and purposeful.
Understanding in HTML is essential for clean, predictable text rendering. Use it only when necessary, and prefer CSS for layout and spacing. When applied correctly, preserves meaning and improves readability across devices.