Developer tools. No fluff.
Free browser-based tools for developers. Generate GUIDs, encrypt and decrypt text with AES, SHA, Base64 and more. No server. No tracking.
Most developer utility sites work the same way: you paste something in, a server somewhere processes it, and a result comes back. That round trip is invisible most of the time, right up until what you pasted was an API key, a customer record, or a real encryption key you didn't mean to hand to a third party's backend.
Every tool on KeyForge runs the other way. Generation, encryption, hashing, and formatting all happen in your browser, using the Web Crypto API for anything cryptographic. There is no server-side processing step to skip, which means there's nothing to trust beyond the code itself: open your browser's network tab while using any tool here and you won't see a request fire.
Built by Frederick Niekerk at ShellRick Tech.
GUID / UUID Generator
Generate UUID v1, v4, and v5 identifiers, in bulk.
Encrypt / Decrypt
AES encryption, SHA/MD5 hashing, Base64, Hex, ROT13.
Password Generator
Generate strong, random passwords.
JSON Formatter
Format, validate, and beautify JSON.
JWT Decoder
Decode and verify JSON Web Tokens.
Coming Soon
Tools we're planning to add next, all running client-side, just like everything else on KeyForge.
Regex Tester
Test regular expressions against sample text with live match highlighting and group capture.
Timestamp Converter
Convert between Unix timestamps, ISO 8601, and human-readable dates across time zones.
Cron Expression Builder
Build and validate cron expressions with a plain-English description of when they will run.
Frequently Asked Questions
Is this GUID generator free to use?
Yes. All tools on KeyForge are free, with no account, rate limit, or usage cap.
Are my keys, plaintext, or generated GUIDs sent to a server?
No. Every operation (UUID generation, encryption, decryption, and hashing) runs locally in your browser using the Web Crypto API. Nothing is transmitted to or stored on our servers.
Which UUID version should I use?
Use v4 for general-purpose unique identifiers: it is random and collision-resistant. Use v5 when you need the same input to always produce the same UUID (e.g. deriving an ID from a URL). Use v1 only if you specifically need a timestamp-ordered identifier.
Should I use AES-CBC or AES-GCM?
Prefer AES-GCM when available. It provides authenticated encryption, meaning any tampering with the ciphertext is detected automatically on decryption. AES-CBC encrypts the data but does not verify its integrity on its own.
Is MD5 or SHA-1 safe to use?
Not for security-sensitive purposes. Both have known collision vulnerabilities and are unsuitable for password hashing or digital signatures. They remain fine for simple checksums where security is not a concern. Use SHA-256 or SHA-512 instead.
Is Base64 encoding the same as encryption?
No. Base64 (and hex) encoding is a reversible text representation with no key and no security: anyone can decode it instantly. Use AES if you need actual confidentiality.