Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
“Hidden options” is informal shorthand for WordPress options that exist in the Options API but are not displayed as fields on a familiar Settings page. Administrators can inspect many of them at the built-in All Settings Screen, located at /wp-admin/options.php. That screen is documented, not a secret backdoor—and an unfamiliar option should not be changed until you know which plugin, theme, or WordPress component owns it and what its value controls.
What “hidden options” means in WordPress
WordPress separates configuration storage from the screens used to edit it. Core, themes, and plugins create named options through the Options API. An option can be a single value or a compound array, and it is stored under its option name in the database.
- Stored option: the value maintained by WordPress or an extension.
- Settings field: a labeled control, such as a checkbox or text box, registered on an administration page.
- Administrative screen: a page that lets an authorized user inspect or edit existing options.
Because these layers are different, a value can exist in the database without having a visible control under Settings. WordPress 3.0 removed the old Settings > Miscellaneous screen; the Options handbook cites upload_url_path as an example of an option no longer reachable through an ordinary settings page. That historical example does not mean the option is appropriate for every current installation.
How to find hidden settings in WordPress
Open the All Settings Screen
- Sign in with an account that has the required administrative capability.
- Open
https://your-site.example/wp-admin/options.php, replacing the domain with your site’s address. You can also open/wp-admin/options.phprelative to the site. - Use the browser’s find command to search the option names shown on the page.
- Identify the owner and documented meaning of an option before editing it.
- Save only a value you have verified, and keep a record of the previous value so you can restore it if necessary.
WordPress calls this route the All Settings Screen. The Options handbook says it can view and change almost all options listed in that handbook. It is not a guarantee that every setting created by every plugin or theme will appear in a consistent, self-explanatory list.
#1 Best Overall
Why a plugin setting may still be absent
An extension may store configuration in custom tables, post metadata, user metadata, files, or an external service instead of a standard option. It may also register an option but provide its own administration page, or hide a field based on license state, user role, environment, or another setting. Check the extension’s documentation and code before assuming that a missing field is an editable option.
Where WordPress options are stored
On a single-site installation, options normally reside in the wp_options table; the wp_ prefix can differ on your site. Multisite network-wide options use the wp_sitemeta table instead. Use the APIs or a documented administration screen rather than editing arbitrary database rows directly.
Option names and values are application data, not self-explanatory labels. A serialized array, JSON string, URL, or numeric flag may have strict expectations enforced by the component that reads it. A syntactically valid value can still disable a feature, break URLs, or cause repeated errors.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
All Settings Screen versus Settings API
| Approach | Best for | What it does | Main consideration |
|---|---|---|---|
All Settings Screen (/wp-admin/options.php) |
An administrator inspecting or adjusting an existing option | Exposes many stored options through a built-in administrative form | Understand the option’s owner and semantics; “almost all” does not mean every extension’s configuration on every site |
| Settings API | A developer adding a setting to an administration page | Registers an option and organizes its fields into pages and sections | Register the option and fields correctly, then rely on the API’s capability and form-security flow |
How developers make an option visible
The Settings API is the documented presentation and form-management layer. A developer registers an option, adds a settings section, and adds fields to an administration page. The handbook recommends calling register_setting() and the add_settings_* functions from an admin_init callback. An option used by a field must be registered for the API to save it.
A typical implementation also calls settings_fields() when rendering the form. That function outputs hidden fields used by the settings form, including the security data needed for submission. The form posts to options.php, where WordPress performs capability checks. Users need the manage_options capability for this Settings API submission flow; on multisite, they must be Super Admins. This requirement applies to that documented flow, not automatically to every custom administration page.
Registration details and arguments are documented in the Settings – Common APIs Handbook, the Using Settings API – Plugin Handbook, and the register_setting() reference.
Should you change an option you found?
Only change it when you can answer all of these questions:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Which WordPress component, theme, or plugin created and reads it?
- What data type and allowed values does that component expect?
- Does the value apply to one site or the entire multisite network?
- What is the rollback path if the change causes an error or blocks the dashboard?
- Have you recorded the original value and tested the change on a staging copy where possible?
Back up the database before making a consequential change, and make one change at a time. If the option belongs to a plugin, use that plugin’s documented UI or support guidance when available. Do not infer a safe value from an option’s name alone, and do not paste guessed serialized data into the form.
Can autoloaded options slow down WordPress?
Yes. Autoloaded options are loaded on every page request, so a large collection can add work before a request is handled. WordPress’s optimization guidance states: “Having too many autoloaded options can slow down your site.” It gives a general recommendation to keep the total under 800 KB (WordPress Developer Resources, 2025), not a universal pass/fail limit for every host or workload. Persistent object caching can improve option retrieval, but it does not make oversized or unnecessary data free.
Rank #4
Choose autoload based on usage
An option needed on most requests may benefit from autoloading. A large value used only on an occasional administration screen generally should not be loaded for every visitor. Evaluate frequency of use, value size, and the site’s object-cache setup together rather than flipping the setting simply because an option appears in the All Settings Screen.
The current add_option() reference uses a nullable Boolean $autoload parameter:
trueloads the option at startup.falseprevents startup loading.nulllets WordPress apply its default heuristics.
Legacy 'yes' and 'no' strings remain accepted for backward compatibility but are deprecated; the reference records that deprecation in WordPress 6.7.0 and the default change to null in WordPress 6.6.0. See the Optimization – Advanced Administration Handbook and add_option() reference for the version-sensitive details.
Best Value
A safe troubleshooting workflow
- Describe the missing control. Note the feature, expected screen, and the WordPress, theme, and plugin versions involved.
- Identify the owner. Search the component’s documentation or source for the option name and its registration code.
- Check scope. Determine whether the value is site-specific or network-wide and whether the current account has the necessary capability.
- Prefer the supported interface. Use the plugin’s settings page or a documented command/API when one exists.
- Back up and stage. Save the original value and test on staging before changing production.
- Verify the result. Test the affected feature, frontend behavior, scheduled tasks, and error logs.
- Rollback cleanly. Restore the recorded value or the backup if the change produces unexpected behavior.
Official references
- Options – Common APIs Handbook
- Settings – Common APIs Handbook
- Using Settings API – Plugin Handbook
- Optimization – Advanced Administration Handbook
add_option()– Functionregister_setting()– Function
Frequently Asked Questions
What is the All Settings Screen in WordPress?
It is the documented administrative route at /wp-admin/options.php for viewing and changing many stored options. It does not promise to list every setting supplied by every plugin or theme.
Why can’t I see a plugin setting in the WordPress dashboard?
The plugin may use a custom page or storage system, conditionally hide the field, or store configuration outside the Options API. Consult its documentation or source before editing an option directly.
Where are WordPress options stored?
Single-site options normally use the wp_options table, while network-wide multisite options use wp_sitemeta; table prefixes can differ.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteThe Bottom Line
Use /wp-admin/options.php as an inspection tool, not as a guessing game: identify the option’s owner, scope, data format, and rollback plan before changing it. Developers should expose supported controls through the Settings API, and should choose autoload behavior according to actual usage and value size.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
