Developer Tools

51 tools

Five small tools that run entirely in the page. Nothing is uploaded, which is the reason to use them on a production API response or a real cookie jar rather than pasting that material into a site that processes it on a server.

Free to use with no account. JSON, password and 2FA tools run entirely in your browser.

5 tools

About

Five small tools that run entirely in the page. Nothing is uploaded, which is the reason to use them on a production API response or a real cookie jar rather than pasting that material into a site that processes it on a server.

Local processing, and what it actually buys you

The value is not speed, it is that sensitive material never leaves the machine. An API response with customer records, a cookie jar that is a live session, a header from a suspicious message: all of these are things you should hesitate to paste into a website. Running the transformation in the page removes that hesitation, and it is why these tools are worth using over a server side equivalent.

The combinations that come up

When debugging an API, the formatter shows the structure, the URL coder handles the query parameters, and the timestamp converter reads the expiry inside a token. Each is small on its own and the sequence is what saves the afternoon.

Clear the box afterwards

A cookie paste is usually a live session that would sign someone in, and API responses often carry tokens. Neither is transmitted anywhere, but neither disappears on its own either, so on a shared machine the last step is emptying the field.

Reading a token without trusting it

A JSON Web Token is three base64url segments joined by dots. Decoding the middle one with the URL tool and pasting the result into the formatter shows its claims, and the timestamp converter turns the exp field into a date you can read. None of that verifies the signature, so a decoded token tells you what it claims, not whether the claim is genuine.

FAQ

Is any of this sent to a server?

No. JSON, URL encoding, timestamps, user agents and cookies all run in your browser.

Why does the tab slow down on a large input?

Because your browser is doing the work. A very large JSON document competes for the memory that tab has, and that is a local limit rather than a quota.

Related tools

Format JSON, encode URLs, convert timestamps, parse a user agent and convert cookies. All of it runs in your browser.