Migrating a site (changing domain or URL)
Moving WordPress to a new domain means rewriting URLs stored all over the database — and many of them sit inside PHP serialized data, where a blind find-and-replace corrupts the byte-length prefixes. Do it safely: run WP-CLI's serialization-aware search-replace across the whole database, or edit a single stored value by hand with Serialized Search-Replace. If a previous replace already broke a value, repair it with Fix Serialized Data. To read or edit a value as JSON, use Serialize / Unserialize or Serialized ↔ JSON.
Setting up wp-config.php
Generate a complete wp-config.php with your database settings, hardening flags and a fresh set of keys — or grab just the eight security values from the WordPress Salts generator. Rotating the salts is also the quickest way to force every user to log in again.
Locked out of an account
No email access to reset a password? Generate a WordPress-compatible phpass hash and drop it into wp_users by SQL, or run a one-line reset with the WP-CLI builder.
Server & performance
Rebuild a lost permalinks file or add HTTPS, redirects, caching and hardening with the WordPress .htaccess generator, and check individual rewrite rules with the .htaccess Tester. Turn post titles into clean permalinks the way WordPress does with the Slug generator, and build avatar URLs with the Gravatar hash tool.
Why browser-based?
These tools handle exactly the data you don't want to hand to a random website — database dumps, password hashes, config secrets. Because every one of them runs client-side, nothing you paste leaves your machine. See about ToolDrops for how that works.