Developer Tools
Generators and converters that save you looking up syntax.
These are the small utilities you reach for a few times a month and never quite memorise: the exact rewrite condition that avoids a redirect loop, the correct robots.txt directive, the right way to hash a password for Apache basic auth.
Each one generates output you can paste straight into a config file or a template, and each page explains what the output actually does — because pasting a configuration you do not understand into a live server is how sites go down.
- .htaccess Generator Build Apache rules for HTTPS, www canonicalisation, WordPress permalinks, security and caching — with the traps flagged before you deploy.
- robots.txt Generator Build a robots.txt for WordPress, an online store or a general site, with sitemap declaration and optional AI crawler blocking.
- Meta Tag Generator Generate the full head block for a page, with live character counts against the limits that actually apply.
- JSON Formatter & Validator Format JSON for reading, minify it for shipping, and get a specific explanation when it fails to parse.
- Password Generator Generate passwords using the operating system random source, with look-alike characters excluded.
- Hash Generator Generate checksums in six algorithms, with a clear note on which are safe for what.
- Base64 & URL Encoder Convert text between Base64, percent-encoding and HTML entities in both directions.
- UUID Generator Generate random UUIDs, with a note on what they cost as database keys.
- URL Slug Generator Convert a title into a URL-safe slug, with optional stop-word removal.
- .htpasswd Generator Generate a bcrypt-hashed user line plus the matching .htaccess block.
Tools for the things you look up every time
Nobody remembers the exact RewriteCond for forcing HTTPS without breaking an existing rule. Nobody remembers whether it is Disallow: with a blank value that allows everything or blocks it. These are the details you look up, paste, and forget again by next month.
That is what this category is for. Each generator produces working output and, more usefully, explains the parts that commonly go wrong.
The generators
.htaccess Generator builds Apache and LiteSpeed rules for HTTPS, www canonicalisation, WordPress permalinks, security headers and caching. Rule order matters enormously here and gets it wrong silently — a redirect placed above the WordPress block will loop, and the symptom is a browser error that names neither rule.
robots.txt Generator produces a file for WordPress, a store, or a general site, with sitemap declaration and optional AI crawler rules. The single most expensive mistake on the web is Disallow: / surviving a staging launch, so it is worth generating deliberately rather than copying.
Meta Tag Generator writes the full head block with Open Graph and Twitter tags, measured against real width limits rather than character counts.
.htpasswd Generator produces a bcrypt user line and the matching directory block, for when you need a directory closed off in the next two minutes.
The converters
JSON Formatter reformats for reading or minifies for shipping, and when it fails it tells you which character on which line broke it rather than just refusing. Base64 & URL Encoder converts in both directions across three encodings. URL Slug Generator turns a title into something safe for a path. UUID Generator produces random identifiers, with an honest note about what they cost as a clustered database key.
On the security ones
The Password Generator uses the operating system random source, not a language-level pseudorandom function. That distinction matters: rand() output is predictable given enough samples, and a password generator built on it produces passwords that look fine and are not.
The Hash Generator offers six algorithms and is explicit that MD5 and SHA-1 are broken for anything security-related. They remain useful as checksums for detecting accidental corruption. They are not suitable for storing a password, and no free tool should present them as though the choice were merely a preference.
Nothing you enter into any of these leaves your session. The password and hash tools in particular process input and discard it — there is no log line, no database row and no analytics event containing what you typed.
Common questions
Is it safe to generate passwords on a website?
It depends entirely on the site, which is an unsatisfying answer. This one generates using the operating system random source and never stores or transmits the result — but you cannot verify that from the outside. For a password protecting something that matters, a local password manager is the better habit. For a throwaway account, this is fine.
Can I use the generated .htaccess commercially?
Yes. Everything these tools produce is yours, with no attribution required. It was generated from your input for your use.
Why does my .htaccess cause a redirect loop?
Almost always rule order. A rule that redirects to HTTPS placed after a rule that rewrites to index.php will re-enter the first rule on every pass. The generator emits rules in a working order and flags the combinations that conflict, which is most of the value it adds over a copied snippet.
Which hash should I use for passwords?
None of these. Password storage needs a deliberately slow algorithm with a per-password salt — bcrypt, scrypt or Argon2 — which is what the .htpasswd generator uses. MD5 and SHA-256 are fast by design, and fast is exactly wrong when an attacker is guessing billions of candidates.
Does the JSON formatter send my data anywhere?
No. It is processed to produce the formatted output and then discarded. Nothing is stored and nothing is logged. That said, if you are formatting something genuinely sensitive, a local editor is the right instinct on any website.
Why block AI crawlers in robots.txt?
Some publishers want their work excluded from training data or from being summarised without a visit. Others want the visibility as more people search through AI assistants. The generator offers the rules for both choices without pushing one, because it depends on what your site is for.