wp-config.php Generator

Build a correct wp-config.php without copy-pasting from a 2014 blog post

Runs in your browser. Nothing is uploaded.

Database

Database name Database user Database host Table prefixChanging this on a NEW install is fine. Changing it on an existing site requires renaming tables and rewriting two option rows — it is not a config change.

Debugging

Enable WP_DEBUGLogs PHP notices, warnings and errors. Pairs with the two options below — never enable it alone on a live site. Write errors to wp-content/debug.logRecommended. Errors go to a file instead of the page. Hide errors from visitorsSets WP_DEBUG_DISPLAY false. Without this, WP_DEBUG prints PHP errors — including your server's absolute paths — to anyone loading the page. Log database queries (SAVEQUERIES)Useful when hunting a slow page. Costs memory on every request — turn it off again afterwards.

Hardening

Disable the theme & plugin file editorDISALLOW_FILE_EDIT. If an admin account is ever compromised, the built-in editor is how a PHP backdoor gets written. There is no good reason to leave it on. Force SSL for the admin areaFORCE_SSL_ADMIN. Only enable once HTTPS actually works, or you will lock yourself out. Enable automatic core updates

Limits

WP_MEMORY_LIMIT (MB) Post revisions to keep0 disables them. Unlimited revisions are the quiet reason many wp_posts tables get enormous.

wp-config.php

Salts are generated in your browser with crypto.getRandomValues(). They are never sent anywhere — but for the record, WordPress's own api.wordpress.org salt endpoint is equally fine; it returns fresh random values over TLS.

About the wp-config.php Generator

Generate a wp-config.php with the constants you actually need — debug logging, memory limits, file-edit lockdown, upload limits, table prefix, and fresh salts. Everything is generated in your browser; nothing is sent anywhere.

Not sure what a setting does or where it goes? Our wp-config.php guide explains each part of the file and how to edit it safely.

WordPress WP_DEBUG Code Generator for wp-config.php

Turn on the debug log without breaking your live site

WordPress Max Upload Size Fixer for php.ini & .htaccess

Raise the upload limit — and get all three values consistent

WordPress .htaccess Generator

The rules WordPress needs, plus the hardening rules it does not ship with

FAQ

Questions

Is it safe to generate wp-config.php salts in a browser?

Yes. The salts are produced with crypto.getRandomValues(), the browser's cryptographically secure random number generator, and never leave your machine. For the record, WordPress's own api.wordpress.org salt endpoint is equally safe — it returns fresh random values over TLS. This is a convenience, not a security fix.

Why does this not ask for my database password?

Because you should not type a production database password into a web page, however trustworthy it claims to be. The generated file has a placeholder — fill it in locally, in your editor.

Can I change the table prefix on an existing site?

Not by editing wp-config.php alone. Changing $table_prefix on a live site requires renaming every table AND rewriting two rows in the options and usermeta tables. Change it on a fresh install, or leave it alone.