About Softkey Tools

Most developer utilities on the web are a text box and a button. They convert the value and tell you nothing. When something then goes wrong in production, the person using the tool is no better equipped than before: they still do not know that Base64 is not encryption, that decoding a JSON Web Token proves nothing about its signature, or that a missing quiet zone is why a printed barcode will not scan.

We build the opposite. Each of the 23 tools here is paired with a written explanation of the underlying format or algorithm, worked examples with real values, a reference table, the mistakes that cause the bugs, and answers to the questions people actually ask. The intent is that you leave understanding the format, not just holding a converted string.

A second principle is that nothing you paste is uploaded. Payloads, tokens, private keys, and Wi-Fi passwords are exactly the kind of data developers need to inspect and exactly the kind that should never be sent to someone else's server. Every conversion, hash, signature, and barcode on this site is computed in your browser with standard web APIs.

The site is a statically rendered Angular application. There is no account system, no analytics profile built from your input, and no server-side processing of tool data. Hashing uses the Web Crypto API, random values come from the browser cryptographically secure generator, and the barcode and QR encoders are implemented from the published specifications rather than pulled from a third-party service.

Because there is no backend for tool data, the site keeps working with the network disconnected once a page has loaded, and there is no usage quota, rate limit, or sign-in.

Explanations are written against primary sources: the IETF RFCs, the ISO and NIST publications, the GS1 general specifications, and the MDN reference for browser behaviour. Every tool page links the specifications it is based on so a reader can check the claim rather than take our word for it.

Example values are computed and verified rather than illustrative. The hash digests shown on the SHA-256 and MD5 pages are published test vectors, the barcode and QR examples are generated by the same encoders the site ships and then read back with an independent decoder, and the timestamp examples are converted rather than approximated.

Where a tool touches security, the page states the boundary plainly: what the tool proves, what it does not prove, and which decision belongs in your backend instead. We would rather lose a click than have someone authorise a request on the strength of a decoded token.

Softkey Tools is published and maintained by Softkey Solutions Ltd, a software development company. The site is maintained by its engineering team, who build and support production web and integration software, which is where the workflows behind these tools come from.

For corrections, questions about a tool result, advertising, or privacy requests, write to support@softkeylabs.com. We welcome corrections in particular: if a specification reference or a worked example on this site is wrong, tell us and we will fix the page.