Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Guide

How to Reduce Autoloaded Options in WordPress

Short answer

To reduce autoloaded options in WordPress, open Tools, then Site Health, and check the total size. List the largest rows with WP-CLI or a database query, find the plugin that owns each large row, and turn autoload off for rows that are not needed on every request. Keep the total under 800 KB as of November 2026.

Key takeaways

  • WordPress Site Health marks autoloaded options at or above 800,000 bytes as a critical issue as of November 2026.
  • WordPress 6.6 added the values on, off, auto, auto-on and auto-off, and stops autoloading new options larger than 150,000 bytes without an explicit choice.
  • Turning autoload off keeps the option value in the database and loads it only when code asks for it.
  • Transients without an expiry are autoloaded, while transients with an expiry are not autoloaded.
  • Back up the database before you change any row, and change one option at a time.
  • Never turn off or delete core options such as siteurl, home, active_plugins and rewrite_rules.

What are autoloaded options in WordPress?

Autoloaded options are settings stored in the wp_options table that WordPress loads into memory on every request, before it knows which page to show.

An option is a named value in the WordPress database. WordPress describes autoloaded options as configuration settings for plugins and themes that load with every page, in its Optimization guide.

WordPress gathers the autoloaded rows into one set called alloptions. Code can then read a value from memory instead of asking the database again for each setting.

The Options API stores site settings, theme settings, widget settings and plugin settings as rows in wp_options. Each row has a name, a value and an autoload flag that decides if it joins that early set.

Why do autoloaded options slow down a site?

They slow a site because WordPress reads the whole autoloaded set in one query on every request, so a large set adds work before any page can start.

WordPress VIP explains that every option marked for autoload is fetched and stored in memory for each request, and that large, rarely used or often changing options should not autoload. See the WordPress VIP autoloaded options guide.

That early load matters most on uncached requests, when no page cache can skip the database step. If you are working through speed in general, start with how to speed up WordPress and treat autoload as one item in that list.

A persistent object cache helps here. WordPress notes that without one, the server must read options from the database for every page view, which slows response times such as Time to First Byte.

How large is too large for autoloaded options?

Aim to keep autoloaded options under 800 KB, because WordPress Site Health marks a total at or above 800,000 bytes as a critical issue.

The Site Health test counts the rows in alloptions and adds up their size. Its filter is called site_status_autoloaded_options_size_limit, and the default limit is 800,000 bytes, as shown in the Site Health autoloaded options reference.

The 800 KB line is a warning level, not a hard limit for every site. A small site can sit well below it, while a large store with many settings may need a closer look even near it.

Size alone does not prove that autoload is your main speed problem. Check it next to other page checks in how to pass Core Web Vitals in WordPress before you change database rows.

What changed in WordPress 6.6 for autoload values?

WordPress 6.6 replaced the old yes and no autoload values with on, off, auto, auto-on and auto-off, and added a size rule for new large options.

The WordPress 6.6 dev note says WordPress loads multiple options with a single query on each request, and that the old default of yes left many options loading on every page for no reason. Read the change in the WordPress 6.6 Options API dev note.

Stored valueMeaning
yesLegacy value, still treated as autoloaded
noLegacy value, not autoloaded
onExplicit choice to autoload
offExplicit choice not to autoload
autoNo explicit choice, WordPress decides, currently loaded
auto-onWordPress decided to autoload
auto-offWordPress decided not to autoload

WordPress still treats legacy yes rows as autoloaded. The function wp_autoload_values_to_autoload returns yes, on, auto-on and auto by default, so include all four in any count.

A new size rule also applies. When code saves an option without an explicit autoload choice, WordPress will not autoload it if the value is larger than 150,000 bytes, using the wp_max_autoloaded_option_size filter.

The old yes and no values were deprecated in WordPress 6.7, and add_option now defaults to null, which lets WordPress decide. Use true or false in new code instead of yes or no, as shown in the add_option reference.

How do you check the size of autoloaded options in Site Health?

Open Tools, then Site Health, then Status, and look for the autoloaded options result, which shows the count and the total size.

  1. In the WordPress admin, go to Tools, then Site Health.
  2. Open the Status tab.
  3. Find the result labelled Autoloaded options are acceptable, or Autoloaded options could affect performance.
  4. Note the number of autoloaded options and the total size shown in the text.

If the result says the total is acceptable, the size is below 800,000 bytes. If it says autoloaded options could affect performance, the total has reached that limit, as shown in the Site Health autoloaded options reference.

Site Health gives you the total, not the list of rows. A critical result means you should list the largest rows before you change anything.

For a wider check on slow hosting, see how to tell if your host is slowing WordPress down.

How do you find the largest autoloaded options with WP-CLI?

Run wp option list with the autoload filter and the size fields, then sort the result so the largest rows come first.

wp option list --autoload=on --format=total_bytes
wp option list --autoload=on --fields=option_name,size_bytes

The first command gives the total size. The second lists each autoloaded option name with its size in bytes, so you can see which rows deserve a closer look.

WP-CLI is the command line for WordPress. Its own site says anything you can do in the WordPress admin, you can do from the terminal.

If you prefer a visual check, Query Monitor groups database queries by the responsible plugin, theme, or function. That grouping helps you trace a large option back to its owner.

Use the option name to find its owner. Most plugins prefix their option names with their own slug, so a name that matches a plugin you removed is a strong lead.

Many large rows come from plugins that were added and never removed cleanly. If the list is long, read how many plugins is too many for WordPress before you add more.

How do you find the largest autoloaded options with a database query?

Run two read-only SQL queries in phpMyAdmin or a database tool: one for the total size and one for the 20 largest rows.

SELECT COUNT(*) AS autoloaded_rows, ROUND(SUM(LENGTH(option_value)) / 1024) AS autoloaded_kb FROM wp_options WHERE autoload IN ('yes', 'on', 'auto-on', 'auto');
SELECT option_name, LENGTH(option_value) AS bytes FROM wp_options WHERE autoload IN ('yes', 'on', 'auto-on', 'auto') ORDER BY bytes DESC LIMIT 20;

Replace wp_ with your own table prefix if it differs. The queries use yes, on, auto-on and auto, which are the four values WordPress treats as autoloaded by default, as listed in the WordPress 6.6 Options API dev note.

These queries only read data. Do not run an UPDATE or DELETE from the same screen until you have a backup and have checked the owner of each row.

How do you turn off autoload for one option safely?

Turn autoload off for one named option at a time, keep its value in the database, and check the site after each change.

  1. Back up the database, or export the wp_options table, before you change anything.
  2. Identify the plugin or theme that owns the option, and confirm the option is not needed on every page.
  3. Run wp option set-autoload option_name off, using the exact option name.
  4. Clear the object cache if you changed a row by hand in the database.
  5. Check the front end and the admin, then check Site Health again.

The WP-CLI command accepts on, off, yes and no, and has been available since WP-CLI 2.8.0. The example in the wp option set-autoload reference uses wp option set-autoload abc_options no.

In PHP, wp_set_option_autoload changes one option without changing its value, and wp_set_option_autoload_values changes several at once. Both were added in WordPress 6.4, as shown in the wp_set_option_autoload_values reference.

If you prefer the dashboard, the Performance Lab plugin from the WordPress Performance Team extends the Site Health check with a table of the largest rows and a way to switch autoload off there. See the Performance Lab plugin page.

Turning autoload off does not delete the option. WordPress VIP notes that code which needs the value will fetch it from the database on first use, then cache it separately. See the WordPress VIP autoloaded options guide.

Which options should you never turn off or delete?

Never turn off or delete core options that WordPress needs on every request, such as siteurl, home, active_plugins and rewrite_rules.

WordPress VIP gives the rule behind that list: autoload the options most requests need, and do not autoload large, rarely used or often changing values. Use that test for each row, not its size alone. See the WordPress VIP autoloaded options guide.

  • siteurl and home: the site address WordPress uses on every request.
  • active_plugins: the list of plugins WordPress must load.
  • rewrite_rules: the rules WordPress uses to match URLs to pages.
  • wp_user_roles: the roles WordPress checks for logged-in users.

If you do not know what an option does, leave its flag alone. Search the option name in the plugin docs or support forum, and ask the plugin author if the name gives no clue.

How do you clean up options left by removed plugins?

Delete an option only after you confirm its plugin is gone, you have a backup, and the option is not shared with another active plugin or theme.

  1. List the largest autoloaded rows and match each name to a plugin prefix.
  2. Check that the plugin is removed, not just deactivated, since deactivation alone does not remove its rows.
  3. Use the plugin uninstall step first if it is still installed, so it can remove its own data.
  4. If the plugin is already gone, delete one row with wp option delete option_name.
  5. Check the front end and the admin after each deletion.

WordPress VIP lists delete as one step after backup and audit, and only for a problem option you have checked. See the WordPress VIP autoloaded options guide.

Delete one row at a time and check the site between deletions. A bulk delete can remove a row another plugin still reads.

How do you stop autoload bloat from coming back?

Stop new bloat by setting autoload to false for admin-only settings, giving every transient an expiry, and rechecking Site Health after plugin changes.

Transients are a common source of growth. WordPress notes that transients without an expiry are autoloaded, while transients with an expiry are not, so always set an expiry. See the Transients API introduction.

When you write plugin code, pass false for settings that only one admin screen reads. The add_option reference recommends true only for options used across several places on the front end, and false for options used on few specific URLs. See add_option.

A persistent object cache does not shrink the autoloaded set, but it makes loading options faster. WordPress notes that it saves database trips on every page view, in its Optimization guide.

Keep the wider page size in view too. Large autoloaded data often sits next to large page payloads, so read how to avoid enormous network payloads in WordPress if front-end size is also high.

What mistakes should you avoid?

Avoid deleting the largest rows first, switching off autoload in bulk, and changing rows without a backup.

  • Deleting the largest row before you know its owner, since the plugin may need it to run.
  • Turning autoload off for every large row at once, which makes it hard to find the change that broke a page.
  • Querying only autoload equals yes, which misses on, auto-on and auto rows on WordPress 6.6 and later.
  • Changing rows in the database by hand and forgetting to clear the object cache.
  • Treating 800 KB as proof that autoload is the cause, when the total is only a warning level.

Work through the list one row at a time. Back up first, change one flag, check the site, and only then move to the next row.

Frequently asked questions

What is a good size for autoloaded options in WordPress?

Aim for under 800 KB in total. WordPress Site Health uses 800,000 bytes as its warning limit, so a total below that line is marked acceptable. A total at or above that line is marked as a critical issue, which means you should list the largest rows and review them, not delete them at once.

Does turning off autoload delete my plugin settings?

No. Turning autoload off keeps the value in the database and only stops WordPress loading it on every request. The plugin or theme that owns the option will still fetch the value when it needs it. That is why switching autoload off is safer than deleting a row you have not checked.

Why is my autoloaded total still high after WordPress 6.6?

WordPress 6.6 only changed how new options are saved. Rows written before that update keep their old autoload values, and a plugin that explicitly asks for autoload still gets it at any size. Old large rows stay in the set until you review them and turn autoload off for the ones you do not need on every page.

Can I delete autoloaded options from a plugin I removed?

Yes, but only after a backup and after you confirm the plugin is fully removed and no other plugin or theme shares the option. Delete one row at a time and check the site after each deletion. If you are unsure what a row does, leave it alone and ask the plugin author first.

Do transients count as autoloaded options?

Some do. Transients stored in the database live as rows in wp_options. A transient set without an expiry is autoloaded, while a transient set with an expiry is not. Always set an expiry when you save a transient, and clear expired transients rather than letting them build up.

Will a persistent object cache fix autoloaded options?

No, it will not shrink the autoloaded set. A persistent object cache makes loading options faster by serving them from memory instead of the database on every request. You still need to review the largest rows and turn autoload off for the ones that are not needed on every page.

Sources

  1. Optimization WordPress Developer Resources
  2. WP_Site_Health::get_test_autoloaded_options() WordPress Developer Resources
  3. WordPress 6.6 Options API dev note Make WordPress Core
  4. add_option() WordPress Developer Resources
  5. wp option set-autoload WordPress Developer Resources
  6. Autoloaded options WordPress VIP Documentation
  7. Performance Lab WordPress.org
  8. An introduction to the Transients API WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test