The utilities you reach for in the middle of something else: converting between configuration formats, decoding a value to see what is in it, working out a permission bit or a cron field.
Each has its own page and its own URL, but they are panels inside one product, so moving between them costs no page load.
Two honest limits worth knowing before you arrive. The JWT tool decodes only — it never verifies a signature, so nothing it shows proves a token is genuine. And hashing and UUID generation need a secure context, because that is where browsers expose Web Crypto.
What people use these for
Finding the exact line and column where a JSON document stops being valid.
Converting a docker run command into a compose file.
Reading the claims inside a JWT without pasting it into someone else’s server.
Working out what 755 means, or what to type to get it.
Building a cron expression and seeing when it will next fire.
Encoding base64 correctly for text containing accents or emoji.
Guides for this section
No guide has been written for this section yet. The tools above document what they do and what they cannot do on their own pages.
Privacy in this section
JWTs are live credentials and hashes are often derived from secrets, so nothing typed into these tools is transmitted or logged, and no page of this product carries advertising.