Privvert - private browser-based file toolsPrivvert

HTML-entiteter & Unicode

Kod, dekod, inspiser

Unicode breakdown (23 characters)

CharCode pointUTF-8JS escapeHTML
HU+0048 (72)48\u0048H
eU+0065 (101)65\u0065e
lU+006C (108)6C\u006Cl
lU+006C (108)6C\u006Cl
oU+006F (111)6F\u006Fo
␠U+0020 (32)20\u0020 
-U+002D (45)2D\u002D-
␠U+0020 (32)20\u0020 
wU+0077 (119)77\u0077w
oU+006F (111)6F\u006Fo
rU+0072 (114)72\u0072r
lU+006C (108)6C\u006Cl
dU+0064 (100)64\u0064d
!U+0021 (33)21\u0021!
␠U+0020 (32)20\u0020 
☃U+2603 (9731)E2 98 83\u2603☃
␠U+0020 (32)20\u0020 
©U+00A9 (169)C2 A9\u00A9©
␠U+0020 (32)20\u0020 
2U+0032 (50)32\u00322
0U+0030 (48)30\u00300
2U+0032 (50)32\u00322
5U+0035 (53)35\u00355

Om dette verktøyet

Encode special characters as HTML entities (&, <, ☃) or decode entity-encoded text back to plain Unicode. Includes a per-character Unicode inspector showing code point, UTF-8 bytes and JavaScript escape sequences.

Useful for safely embedding reserved characters in HTML/XML, debugging escaped content from APIs, exploring Unicode characters, and building copy-paste-safe code samples. Runs locally in your browser.

HTML entities exist so characters with special meaning in HTML (<, >, &, ", ') can appear safely inside markup, and so non-ASCII characters can survive transports that mangle UTF-8. Privvert converts both named entities (&amp;, &copy;, &euro;) and numeric entities (&#169;, &#x00E9;) in both directions, with full support for emoji and astral-plane Unicode characters.

Funksjoner

  • Encode as named, decimal or hex entities
  • Decode every form of HTML entity
  • Per-character table: code point, UTF-8 bytes, JS escape (\u, \x)
  • Round-trip safe - encode then decode returns the original
  • Browser-only - text never uploaded
  • Free and unlimited

Slik bruker du det

  1. Paste text.
  2. Pick an encoding style (named, decimal or hex).
  3. Copy the encoded or decoded result.
  4. (Optional) inspect each character in the breakdown table.
🔒 100 % privat

Alt skjer inne i nettleseren din med JavaScript og WebAssembly. Filene dine lastes aldri opp, lagres aldri og ses aldri av oss.

Ofte stilte spørsmål

Why use entities?

They let you safely include reserved HTML characters (<, >, &, ") in markup without breaking it. Entity-encoded text always renders as the literal character, never as markup.

Named, decimal or hex?

Named (&) is most readable. Decimal (&) and hex (&) are universally supported and work for any Unicode character. Use named for the common ones, hex/decimal for everything else.

Will modern browsers need entity encoding?

Most modern setups use UTF-8 throughout, so most characters can be written literally. Entities are still essential for the reserved characters (<, >, &, ", ') and useful for invisible characters.

What's the JS escape column for?

When you need to put a Unicode character in a JavaScript string literal - \u00E9 for é, \u{1F600} for 😀 - these escapes work in any JS source.

When do I need to HTML-encode text?

Any time user-controlled text is inserted into HTML markup. Failing to encode is the canonical XSS vulnerability - a comment containing becomes executable script if rendered without encoding. Modern templating engines (React, Vue, Svelte) encode by default; raw string concatenation does not.

What's the difference between HTML entities and URL encoding?

HTML entities encode for HTML context (& for &). URL encoding (%26) encodes for URL context. They are different escape schemes for different parsers - mixing them is a common bug.

becomes executable script if rendered without encoding. Modern templating engines (React, Vue, Svelte) encode by default; raw string concatenation does not."}},{"@type":"Question","name":"What's the difference between HTML entities and URL encoding?","acceptedAnswer":{"@type":"Answer","text":"HTML entities encode for HTML context (& for &). URL encoding (%26) encodes for URL context. They are different escape schemes for different parsers - mixing them is a common bug."}}]}