At a glance
- JSON, four actions: Pretty, Minify, Keys (the top-level field names), Escape (wrap a document as a JSON string).
- HTML: Minify, Strip tags, and two list conversions, to plain lines or Markdown bullets.
- CSS: Minify, plus the same light cleanup steps.
- Decode on sight: JWT, Base64, percent-encoded URLs, escaped JSON strings.
- Nothing is uploaded: a production token never leaves the machine. One-time $19.99, updates included.
The actions follow what you copied
Two rules govern the chips. JSON actions replace each other, because Pretty and Minify are the same document written two ways. The cleanup steps stack instead, so you can collapse spaces and then drop blank lines on one paste.
The Anti-LLM chip is missing from JSON, HTML, CSS and code on purpose. It strips colons and semicolons out of prose, which would turn color: red into color red. Code sets get whitespace and invisible-character cleanup only.
JSON. Pretty indents {"a":1,"b":2} into readable lines. Minify collapses it back. Keys lists the top-level field names, one per line, which is the fastest way to see the shape of a payload someone sent you. Escape turns {"a":1} into "{\"a\":1}" for the times you have to put JSON inside JSON.
HTML and CSS stop at minify and strip. There is no pretty-printer for either one, and I am not going to pretend otherwise. Proper formatting needs a real parser, and a regex that guesses at nesting will eventually mangle a template. Minify collapses the whitespace, Strip tags turns <b>hi</b> into hi, and the list chips turn <ul><li>a</li><li>b</li></ul> into plain lines or - a / - b.
Code that is not JSON, HTML or CSS gets cleanup with no case changes, so identifiers survive: one-line, collapse spaces, remove blank lines, dedupe, sort, strip invisible characters, un-HTML, plus the encode steps.
Decode without a debugger site
Copy the opaque string and Klipto works out the encoding for you. The step where you have to know whether it is Base64, a JWT or percent-encoding disappears, and only the matching decode appears in the row.
JWT: the token decodes to its readable header and payload, so you can check the claims and the expiry in the preview. Base64: VGhpcyBpcyBhIHNlY3JldA== becomes This is a secret. URL: hello%20world%21 becomes hello world!. Unescape: "{\"a\":1}" unwraps back to {"a":1}.
Why the offline part matters for tokens
A JWT carries claims. A payload dump carries customer data. Pasting either into a web formatter hands it to whoever runs that site, and you get to hope their logs are clean. Klipto never sends it, because there is no server in the path. The app reaches the network only to check for updates.
DevUtils, Boop and OK JSON are good apps, and they are destinations. You open one, paste in, pick a tool, copy out, then return to the editor. Klipto puts the same actions in the popup you already opened to paste. For one-off formatting with nothing installed, try it free in your browser.
The same preview handles color conversion, case, links and text cleanup across 22 content types.