JPKCom DB

Convertor PRO

Convertor PRO: text live in 13 encodings (entities, Unicode, UTF-8, NCRs) and data between JSON, YAML, TOML, XML, and INI — JSON numbers stay exact.

Convertor PRO solves two tasks that come up constantly in web development and yet belong closely together: converting characters and encodings, and translating data formats into one another. Both live in one tabbed interface, both run entirely in your browser.

You know the first problem if you have ever wanted to embed a special character into an HTML file, a CSS selector, a URL, or a JavaScript string and weren't sure how to escape it correctly. The emoji that should appear as 😀; the umlaut that becomes %C3%BC in a URL; the é inside a JSON string — these are all representations of one and the same character. Convertor PRO shows you all of them at once.

The second problem is the eternal dance between configuration and data formats: a config.yaml you need as JSON; a TOML block an older system only understands as INI; an XML API response you want to read as YAML. Convertor PRO parses one and emits the other — via a shared intermediate representation, with numbers from JSON kept digit for digit and notices about what the target format cannot express.

The tool is aimed at web developers who want to settle encoding questions fast, at DevOps and config people who shuttle between format worlds, and at anyone working with Unicode, internationalization, or machine-readable data. No account, no installation, no upload to a server.

Tab 1: Encoding — characters and encodings

The Encoding tab shows the same character in 13 parallel notations. You type text into any field — and while you are still typing, all the other fields fill in with their respective representation; the field's Convert button does the same instantly. The conversion is bidirectional and always pivots through the actual characters. It works on whole Unicode code points (an emoji is one unit) and is lossless: whatever you convert into a notation comes back character for character when you convert it back — except for two special cases described in the manual (the Bidi to markup option and the null character U+0000).

Available representations, grouped by theme:

  • Markup & web — HTML/XML (named and numeric entities), Percent encoding (URIs), CSS escapes, JavaScript escapes.
  • Numeric Character References — Hexadecimal NCRs (&#x…;) and Decimal NCRs (&#…;).
  • Code points — Unicode U+hex, 0x… notation, Hex code points, Decimal code points.
  • Encoding bytes — UTF-8 code units and UTF-16 code units.
  • Mixed input — a catch-all field that resolves mixed escapes to characters in a single pass; at the push of a button it also decodes bare hex, decimal, UTF-8, or UTF-16 number sequences.

All HTML5 entities are recognized. The fields for percent encoding, code points, and UTF-8/UTF-16 code units report what they cannot make sense of (an invalid token, a broken UTF-8 byte sequence) in a notice line right below them instead of swallowing it silently; the other fields and Mixed input have no such line and leave invalid values as text or show U+FFFD (�).

Tab 2: Data Formats — JSON, YAML, TOML, XML, INI

The Data Formats tab converts between JSON, YAML, TOML, XML, and INI in any direction. You put your data on the left — Auto-detect works out the source format on its own by test-parsing the input — and pick the target format on the right. The output appears as you type; two syntax-highlighting ACE editors show input and output side by side, and a Swap button flips the direction.

Input errors are reported with line and column plus a button that jumps straight there. And when the target format cannot express something — null in TOML, a nested list in INI, an XML comment — a notice below the editors tells you so. Numbers from JSON stay exact: a 20-digit ID or a 1.0 comes out exactly as it went in (except inside lists that INI writes as a JSON string); numbers read from YAML and TOML don't always (details in the manual). Input by typing, pasting from the clipboard, or opening a file (.json, .yaml/.yml, .toml, .xml, .ini, plus .htm/.html, .cfg, and .conf with automatic detection); output via copy or file download.

Architecture: everything in the browser

Convertor PRO is purely client-side. There is no server round-trip, no API, no upload, and nothing is stored: both the encoding functions and the format conversion run entirely as JavaScript in your browser. The data formats rely on established libraries — js-yaml (opens in a new tab) for YAML, smol-toml (opens in a new tab) for TOML, lossless-json (opens in a new tab) for JSON with exact numbers, and the browser's DOMParser for XML — plus the tool's own modules for the encodings and for INI, coordinated through a shared object intermediate stage. Sensitive configurations or tokens never leave your machine.

Try it now

→ Open Convertor PRO — pick a tab, paste your text or data, read off the result. No account, free, right in the browser.

Closely related from the same code-and-text family:

  • JSON Editor — validate, format, search, and edit JSON when you want to work with a JSON structure more deeply than Convertor PRO is built for.
  • Coder — Base64, URL encoding, Punycode, Quoted-Printable, JWT, and Data URIs: encoding operations that go beyond plain character conversion.
  • Hash Generator — checksums and hashes (MD5, SHA-2/3, BLAKE3, bcrypt, Argon2, and more) when you need a fingerprint of a text rather than another notation of it.

Go deeper on the sub-pages: the Manual with every field and mode in detail, Examples with concrete runs, and collected Tips & Tricks.