Toolstead
Small, focused tools for everyday developer chores — no sign-up, no upload, no tracking. Open DevTools and watch the Network panel: converting anything produces zero requests.
Encoding
Base64 to Image
Paste any Base64 — prefixed, raw, wrapped, URL-safe or broken — and see the image.
Image to Base64
Get the exact string you need: Data URI, plain Base64, CSS, HTML or JSON.
URL Encoder / Decoder
Percent-encoding done right, including the + versus %20 question.
Ascii85 Encoder
Encode text or hex bytes to Ascii85, or decode it back — with the Adobe <~ ~> wrapper handled, not guessed.
JWT Decoder
Split a token, read the claims and see whether it is expired — without ever asking for your key.
Hash Generator
MD5, SHA-1, SHA-256, SHA-384 and SHA-512 from one input, computed in the page.
Hardware
Card Number Converter
Paste any card UID — decimal, hex, reversed or colon-grouped — and see every form of it at once.
Wiegand 26/34/36 Converter
Paste a frame, a hex payload or a card number and see all three Wiegand widths: facility code, card number and both parity bits.
Wiegand Bit Formats
Documented credential layouts, keyed by format rather than by bit count.
Images
Guides
Everything that tends to go wrong when you move an image through Base64 — and how to fix it.
Bit Length Is Not a Format: Five 34-Bit Layouts
A 34-bit Wiegand frame has five published layouts, not one. Decoding an AWID card as HID produces a facility code that looks right and opens nothing.
MIFARE Classic Sector Dump: What the Hex Actually Says
Sixteen bytes per block, one trailer per sector, and a UID stored backwards. What a dump really contains, and the three parts people read wrong.
Duplicate URLs: Why One Page Gets Many Addresses
Trailing slashes, percent-encoding case, default ports and query order. Six differences that split one page into six addresses, and how to collapse them.
Percent-Encoding: The Reserved Characters That Break URLs
Reserved means the character has a job in that position. Leave it unencoded in a value and it splits your data into parameters or fragments, with no error.
Why these tools are built this way
Your data never leaves the browser. Every tool here runs entirely client-side. There is no backend to send anything to — that is the reason the page keeps working when the network drops, and why a 5 MB image convert produces no requests at all.
Failures get explained, not just reported. The Base64 tools do not stop at "invalid input". They tell you the character that broke it, its exact position and code point, whether the length implies truncation, and whether those bytes are gzip rather than an image — then offer a one-click fix where one exists.
Offline by default. The site installs as a PWA, so once a tool has loaded it stays available with the network switched off — useful when you are debugging against an internal service.
No account, no history, no upload. If advertising is introduced later, it will be limited to clearly separated, fixed-height slots that never cover the working area.