Developer Tools
These are the small detours in a working day: a payload that needs indenting before you can read it, a token you want to inspect, a cron line somebody wrote in 2019, a subnet mask you have to justify in a review. Looking each one up costs more attention than the task deserves. Everything here runs inside the browser tab, so config files, access tokens and production dumps stay on your machine, which is the only sane default for anything work-related.
Debugging an API response: the JSON Formatter makes it readable and the JSON Diff shows what changed between two captures, while the JWT Decoder reads the claims and expiry out of a bearer token. Wiring up infrastructure: the Cron Expression Parser translates a schedule into plain English before you deploy it, and the IP Subnet Calculator returns the range, broadcast address and usable host count. For quick conversions there is Base64, the Unix Timestamp Converter and the Hash Generator.
A few results are easy to misread. Decoding a JWT is not verifying it: the payload is only Base64, and a decoder cannot tell you whether the signature is valid. Hashing is one-way, so a hash is not encryption and cannot be reversed. Regular expressions vary by engine, and a pattern that passes here may behave differently in PCRE or Go. Timestamps are shown in UTC and in your local zone, which is worth checking before you file a bug about an hour-long discrepancy.
40 free tools — all run entirely in your browser.
Frequently asked questions
Is it safe to paste production data into an online formatter?
With these tools, yes, because the parsing happens in JavaScript inside your own tab and nothing is sent to a server. You can confirm it by opening the network panel, or by loading the page and then going offline. That said, follow your employer's policy: some teams prohibit pasting customer data into any browser tool regardless of where it runs.
What is the difference between decoding and verifying a JWT?
Decoding splits the token and Base64-decodes the header and payload so you can read the claims, the issuer and the expiry. Verifying checks the signature against a secret or public key to prove the token was not altered. The JWT Decoder does the first, which is what you need when debugging; only your server should do the second.
How do I read a cron expression like 0 */6 * * 1-5?
Paste it into the Cron Expression Parser and it describes the schedule in words and lists the next run times. The five fields are minute, hour, day of month, month and day of week, so that example runs at minute zero of every sixth hour, Monday through Friday. Note that the schedule follows the server's time zone, not yours.