Entités HTML

Encoder / décoder.

Interactive controls load with JavaScript. Processing stays in your browser—nothing is uploaded.

Loading tool…

How to use

  1. Open the tool — Open this LocalKit page and wait for the interactive controls to load.
  2. Provide input — Paste or type your content (or set options). Data stays in the browser.
  3. Run the action — Use the primary button or live controls to generate the result.
  4. Copy the result — Copy the output into your editor, terminal, or documents.

Limits

Requires JavaScript. Extremely large inputs may slow the browser tab. Results depend on your browser APIs; there is no server-side processing quota because nothing is uploaded.

When to use

When you want a quick, free utility without creating an account or sending content to an online converter.

When not to use

When you need server-side integration, batch automation at scale, or certified compliance tooling.

Privacy note

Tool inputs are processed in your browser only. Theme, language and favorites may use localStorage; hosting may keep standard access logs (IP, UA, URL) without tool payloads.

FAQ（5）

Encode vs decode?

Encode turns <>& into entities for safe HTML text; decode restores characters.

Will this sanitize XSS?

Encoding helps when inserting text nodes. It is not a full HTML sanitizer for rich markup.

Is processing local?

Yes. Nothing is uploaded.

Named vs numeric entities?

Both appear in HTML; decoding accepts common named and numeric forms.

Should I encode entire documents?

Usually encode user text fragments, not whole templates with tags you need to keep.