XML entity encoder

Use it free in the browser for config hygiene and content cleanup, or call the API at $0.002 per successful request when pipelines need reproducible XML entity transforms in CI and backend services.

What the five predefined XML entities are and what this tool returns

The JSON response always includes result for the transformed string, mode echoing encode or decode, encoding fixed to xml_entities, and input_length plus output_length so tests can assert sizes. Encode also reports entities_encoded and decode reports entities_decoded so you can confirm how many special characters or named references were rewritten. There is no partial silent skip for unknown complete entities: either every complete &name; is one of the five predefined forms or the request fails with invalid_input.

How text and mode are read and how results stay reproducible

Encode walks the string character by character and replaces only the five special characters with their preferred entity forms, leaving letters, digits, and other Unicode unchanged so readable copy stays readable. Because ampersand is rewritten in the same left-to-right pass as the other specials, you never double-encode an already escaped fragment in a second accidental pass unless you feed entity text back into encode again. Decode scans for well-formed &name; sequences: a letter-started name of letters and digits ending with a semicolon. Numeric forms such as ' and ' are also rejected because they are not among the five predefined named entities this tool implements. Incomplete stubs that start an entity-like sequence without a terminating semicolon fail closed. The preferred payload field is text, with aliases input, value, s, and xml so forms, query strings, and SDK clients can reuse the same contract without renaming columns. Mode defaults to encode and accepts decode explicitly; aliases op, direction, and action map to the same switch for scripts that already use those names, and escape or unescape are accepted as synonyms. Bare ampersands that do not form a complete reference are left untouched so incomplete drafts do not explode, but a complete unknown name such as   or &notanentity; raises invalid_input with a message that names the bad reference. The length ceiling of one hundred thousand characters keeps Worker memory predictable while still covering templates, sample documents, and most paste buffers. Pair the free browser run on this page with the priced API when you need the identical mapping inside an automated pipeline without re-implementing XML entity tables yourself. Invalid inputs return invalid_input and are not charged, which keeps validation cheap while successful transforms remain a fixed item price at $0.002.

Where XML entity encode and decode fit in markup workflows

Developers meet the five predefined XML entities when they embed user text into configuration files, SOAP or REST XML payloads, SVG attributes, RSS and Atom feeds, and any document that must stay well-formed under a strict XML parser. On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split—free interactive exploration and a priced, identical API—matches the rest of the KIT tier-A catalog and lets you move from a classroom demo to an automated pipeline without changing the encoded result. Pair it with XML-to-JSON or HTML entity helpers when you need broader markup conversion, and with other encoding endpoints when you are building a small lab of free, deterministic text tools for CI and documentation.