What interrupts a working session is rarely the hard problem. It is the small lookup: what sits inside this Base64 blob, which day that ten-digit number is, why the pattern misses. Since what gets pasted in tends to be a token or a slice of production data, all eight compute locally.
Which tool should I use?
- JSON Formatter
- For an API response collapsed onto one line, or for finding the comma you left out. It runs the browser's
JSON.parse, so integer IDs beyond 2^53 have already lost precision by the time you see them — do not write the reformatted document back into a database. - Base64 Encoder/Decoder
- Turn the values printed by
kubectl get secretinto something readable, or assemble a Basic Auth credential going the other way. It is a text tool: a PNG or a PEM decodes to bytes that are not UTF-8 and it says so. For those, use Image to Base64 in the image section. - URL Encoder/Decoder
- This one owns the
%XXsequences in URLs and form parameters. The boundary against the previous tool is clean: percent-encoding belongs in the address bar and form bodies, while Base64 turns up in headers, certificates and config files. - Hash Generator
- For checking a checksum from a download page, or confirming two passages are identical. It hashes text rather than a file, which is why the result rarely matches
sha256sumrun against a file. The SHA family needs HTTPS or localhost to be available, while MD5 is pure JavaScript and works regardless. - Regex Tester
- When the pattern is written but you are unsure what else it catches. Matching runs in a Web Worker under a 1.5-second deadline, so a pathological construction like
(a+)+bis aborted with an explanation instead of freezing the tab. - Color Converter
- The mock-up specifies HSL and the stylesheet wants HEX; four sets of fields stay in sync. The RGB and HSL strings paste straight into CSS, whereas
hsv()is not a CSS function and exists here only to line up with your design software. - QR Code Generator
- For turning a link or a Wi-Fi credential into something scannable. Output is PNG, with selectable size and error correction level (L through H). Higher levels survive smudges but hold fewer characters, and exceeding the capacity produces a clear message rather than a stale image.
- Epoch Converter
- For the bare numbers in logs and database columns. Seconds and milliseconds are told apart by digit count — ten or fewer means seconds — and negatives are accepted, so pre-1970 instants read correctly.
Shared limitations
JSON.parse,btoa,crypto.subtleandRegExpare the browser's own implementations, so what you see here is what your code gets from the same engine, limitations included. Regular expressions deserve particular caution: Java, Go and PCRE do not share JavaScript's exact syntax.- All eight work on fragments of text, and only the QR generator produces something downloadable. Tokens you paste live in this tab's memory alone and no request carries them outward; the page itself still loads advertising scripts, and none of your input travels with them.
FAQ
Why does the SHA-256 here differ from the one my terminal prints?
Because the inputs differ. This hashes the UTF-8 bytes of the text box; sha256sum file hashes every byte of the file. The discrepancy is usually a trailing newline, a byte order mark, or the CRLF endings normalised away when you pasted.
Is there an input size limit?
No fixed one; the practical ceiling is the tab's memory. The regex tester is where size shows, since every edit re-runs the match.