#446 · Developer Tool

HTML Entity Inspector

Inspect named, decimal, and hexadecimal character references in HTML source. Each occurrence is decoded in an isolated element and reported with its source position, resulting character, Unicode code point, and reference style. The output helps diagnose double encoding, inconsistent entity styles, and invisible or unfamiliar characters.

Developer Input

Entity and character map
Ad space

How to use this developer tool

  1. Paste source text or load the representative sample.
  2. Adjust the available parsing option when the tool provides one.
  3. Select Inspect Entities or press Ctrl/Cmd + Enter.
  4. Review the summary, issues, and copy-ready output before using it.

What this developer tool does

A reference pattern locates ampersand sequences that end in semicolons. DOM parsing performs standards-based decoding, after which Unicode code points are read with codePointAt rather than UTF-16 code units.

A reference pattern locates ampersand sequences that end in semicolons. DOM parsing performs standards-based decoding, after which Unicode code points are read with codePointAt rather than UTF-16 code units.

This inspector reports explicit character references in source. Literal Unicode characters that were not written as entities are not included.

Example

Input

<p>Tom &amp; Jerry paid &#36;10 for 3 &lt; 5 items.</p>
<p>Copyright &copy; 2026 — emoji: &#x1F680;</p>

Expected result

Run the sample to see a structured report generated by the same processing logic used for pasted input.

Use cases

  • Review front-end source during a code migration.
  • Create a structured handoff for documentation or QA.
  • Catch input-specific issues before committing generated output.

Tips for reliable output

  • Paste the smallest complete fragment that reproduces the case.
  • Use the sample once to confirm the expected input shape.
  • Review warnings instead of treating a clean report as a guarantee.
  • Keep the original source in version control before replacing it.
  • Test generated output in the target browser or application.

Processing details

A reference pattern locates ampersand sequences that end in semicolons. DOM parsing performs standards-based decoding, after which Unicode code points are read with codePointAt rather than UTF-16 code units.

This inspector reports explicit character references in source. Literal Unicode characters that were not written as entities are not included.

Frequently asked questions

Are hexadecimal numeric HTML entities supported?

Yes. References such as &#x1F680; are decoded and labeled hexadecimal.

Does the inspector list literal Unicode characters?

No. It lists explicit ampersand entity references in the pasted source only.

How are multi-code-point decoded values reported?

Each Unicode code point in the decoded value is listed in U+ notation.

Will an entity without a trailing semicolon be found?

No. The inspector intentionally targets semicolon-terminated references to avoid ambiguous matches.

Does decoding an entity execute pasted HTML?

No. A textarea element performs character-reference decoding without running scripts.

Output fields

FieldMeaning
SummaryCount and outcome of the current run
InterpretationWarnings and practical review guidance
ExportsCopy-ready output plus CSV or JSON when available

Explore HTML, CSS & JavaScript Tools

Browse related browser-based utilities for inspecting and transforming front-end source.

View category hub