Measure before deleting. In WordPress, open Tools → Site Health → Info → Directories and Sizes to see the size of the installation, uploads, plugins, themes, database and total site. Then compare that figure with your hosting account’s disk-usage report, which is the authority for the whole account. Make a restorable backup and record a baseline first; investigate large media, local backup archives, caches, logs, staging copies and abandoned plugin data before removing anything.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What WordPress disk usage actually measures
“Disk usage” can describe two different measurements. WordPress reports the files and database that belong to an installation. A hosting panel reports the storage charged against the account. Those numbers often differ because an account may also contain mailboxes, server logs, scheduled backups, staging sites, other domains or another WordPress installation.
As an Amazon Associate I earn from qualifying purchases.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe built-in Site Health screen is the best starting inventory for one site. The WordPress.org Site Health documentation says: “The Directories and Sizes section shows you all the information about where the different elements of your WordPress installation are located and what size those directories are.” Treat it as a map, not as the final quota figure.
Why the core number can be narrower than the host number
WordPress core’s get_space_used() function returns used space in megabytes. Unless a filter changes its behavior, it calculates the value from the uploads directory returned by wp_upload_dir(), using get_dirsize(). That makes the value useful for understanding media growth, but it does not guarantee that it includes every file counted by your host.
#1 Best Overall
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
Multisite installations add a quota check. Before accepting an upload, check_upload_size() checks the remaining site quota and the configured maximum file size. When the quota is exhausted, the upload fails even if another directory appears to have free space. A network administrator must therefore check both the network’s quota settings and the account-level storage report.
Before deleting anything: create a baseline and a recovery path
Storage emergencies encourage rushed deletion. Resist that approach. A file that looks old may be the only copy of a backup, a theme asset, a translated language file or an image referenced by a page that is not currently published.
- Create a recoverable backup. Keep a copy of the database and all files needed to restore the site. Confirm that the archive can be opened and that you know where it is stored. A backup left in the same hosting account protects against a software mistake but does not solve a full-account failure, so keep at least one copy outside the account.
- Record the host’s current figures. Save total disk usage, the quota, database size, inode count if shown, and any per-directory totals. Take a screenshot or export the report so you can compare it after each cleanup class.
- Record the WordPress baseline. Write down the Site Health values for the WordPress directory,
wp-content/uploads, plugins, themes, database and total installation. Note the largest folders and tables rather than relying on memory. - Pause automatic growth where safe. If a backup job is repeatedly creating archives or a debug log is expanding rapidly, stop or adjust that job temporarily after confirming that doing so will not remove your only recovery copy.
Do not begin by selecting a large directory in File Manager and pressing Delete. First establish what created it, whether the live site references it, and how you would restore it.
Use Site Health to locate WordPress’s largest components
Open the Directories and Sizes report
- Sign in with an administrator account.
- Go to Tools → Site Health.
- Open the Info tab.
- Expand Directories and Sizes.
- Record the values for the WordPress directory, themes, plugins, uploads, database and total installation.
The report gives you an installation-level overview without changing files. Look for an obvious concentration: a very large uploads directory points to media or generated image variants; a large plugins or themes figure can indicate bundled assets, backups or abandoned extensions; a database figure that is disproportionate to the files suggests revisions, logs or plugin tables worth examining.
Interpret the totals carefully
Site Health may take time to calculate sizes on a large site. Let the scan finish and repeat it later if a value appears incomplete. Compare like with like: a database size shown in the WordPress report may be the logical database size, while a host may also count database backup dumps stored as files. Likewise, a cache shown under wp-content can be deleted safely only when you know the plugin will regenerate it and the deletion will not interrupt an active backup or deployment.
Confirm the account-level number in your hosting panel
Open the host’s disk-usage, storage, quota or account-statistics page. The exact label varies by provider, but the purpose is the same: identify everything charged to the account. Compare the host total with the Site Health total and explain the difference before cleaning aggressively.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
- Slim durable design to help take your important files with you
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
Account locations that WordPress may not show
- Host-generated backups: daily or weekly snapshots may sit outside the public WordPress directory.
- Email and mailboxes: attachments and old messages can consume more space than the website.
- Web and error logs: verbose logging can grow continuously, especially when a plugin or PHP warning repeats on every request.
- Staging and development copies: a clone may contain a second uploads directory and duplicate database exports.
- Other sites: shared accounts often contain several domains, subdomains or applications.
- Inode limits: a host can reject new files after the account reaches its file-count limit even when gigabytes remain free.
If the host provides a directory tree, sort by size and inspect the largest branches. If it provides only a total, ask support which categories count toward the quota and whether recently deleted files are retained in a trash or snapshot area.
Drill into wp-content without breaking the site
Most WordPress growth is under wp-content. Work from largest to smallest, and open each folder in a read-only analyzer or the host’s size tool before making changes. A read-only WordPress disk-usage analyzer can help identify large directories and database tables, but use it for measurement first; do not grant a cleanup tool permission to delete automatically until you understand its rules.
Uploads organized by year and month
In a standard installation, media is stored under wp-content/uploads, commonly in year and month folders. Sort those folders by size. A single month that is much larger than the surrounding months may correspond to a photo import, a migration, a failed optimization job or a plugin that generated many image variants.
Use the Media Library and page content to determine whether a file is still used. “Unused” in a folder listing does not prove that an image is safe to remove: custom fields, CSS, theme templates, RSS feeds and external landing pages can reference a URL directly. Remove only files you have confirmed are not needed, or move them to an archive outside the hosting account. WordPress housekeeping guidance notes: “Many users upload a lot of graphics to their site that they end up never using.” It recommends moving unused images to a hard-drive folder when server space is limited.
Free tools Windows power users keep installed
One-click scans. No signup required.
Local backup archives
Search for ZIP, TAR, SQL and other export files in wp-content, the account root and staging directories. Keep the number of local generations required by your recovery policy, then move older recoverable copies off-host. Do not delete the newest archive until an external copy has been checked and you have tested that it contains both the database and the files you need.
Cache and optimization directories
Page caches, minified assets, image-optimization working files and temporary exports can be large. Clear them through the responsible plugin or host control panel when possible. That lets the software update its indexes and avoids leaving stale metadata. Manual deletion is appropriate only when the plugin’s documentation or support instructions identify the directory as disposable and no cache rebuild is running.
Rank #3
- High-capacity external hard drive with up to 2TB of storage The ModusTech Facet portable external hard drive gives you dependable HDD storage in a slim 2.5-inch design. Multiple capacities available up to 2TB — back up photos, videos, music, documents, and game libraries with room to grow. A trusted external storage solution for everyday backup, media archives, and creative work.
- USB-C and USB 3.1 connectivity with included 2-in-1 cable The Facet ships with a USB-C to USB-C cable and tethered USB-A adapter, so this external hard drive connects to modern laptops, USB-C iPhones, tablets, and older USB-A computers without buying an extra cable. USB 3.1 Gen 1 (5Gbps) interface delivers real-world transfer speeds up to 100MB/s — fast enough to back up 50GB of files in about 8 minutes.
- Plug-and-play external hard drive for PC, Mac, and laptops Preformatted in exFAT and ready to use the moment you plug it in. The Facet works out of the box with Windows PCs, macOS Macs, MacBooks, Chromebooks, and laptops — no drivers, no software, no setup required. A true plug-and-play external hard drive built for everyday use across every major operating system.
- External hard drive for PS4, Xbox One, and Smart TV gaming The Facet is compatible with PlayStation 4, Xbox One, and Smart TVs with USB support. PS4 and Xbox One games run directly from the drive — plug it in, format through the console, and add to your storage. Also works with Smart TVs that support USB recording or external media playback.
- Slim, shock-resistant portable external hard drive — 160g At 2.5 inches and just 160g, this portable external hard drive is bus-powered through a single USB-C cable — no separate power adapter, no extra cables. Slim enough for a laptop bag, jacket pocket, or camera bag, with a shockresistant casing and faceted diamond-texture top panel that resists fingerprints and everyday wear. Backed by a 1-year limited warranty from ModusTech, a consumer electronics brand specializing in external storage.
Debug and error logs
Look for debug.log, PHP error logs and plugin-specific logs. Open the newest lines and identify the source of repeated messages before truncating or rotating the file. A log that refills immediately indicates an unresolved configuration or code problem; deleting it alone provides only temporary space.
Staging, migration and import folders
Migration plugins and staging tools may leave temporary packages, database dumps or complete copies of wp-content. Confirm that no deployment, rollback or scheduled task still needs them. Remove a staging copy only after checking its hostname, scheduled jobs and backup policy so you do not delete the production site’s recovery environment by mistake.
Reduce media usage safely
Use evidence, not file age
Build a candidate list from the largest files and directories, then verify each candidate. Check the attachment record, the pages and posts that embed it, featured-image settings, menus, widgets, custom fields and theme templates. If the image is required but large, create an appropriately sized replacement and update every reference before archiving the original.
Archive instead of deleting when the decision is uncertain
Move confirmed-but-infrequently-needed media to an archive outside the hosting account. Preserve the original path in an inventory so it can be restored if an old article, campaign or legal record needs it. An external hard drive can serve as an archive destination, but it is not a substitute for a tested backup plan: keep another copy, protect the drive from failure and periodically verify that archived files can be read.
Understand generated variants
One uploaded image can produce several thumbnails and responsive sizes. Deleting one variant may cause a layout to fall back to a larger file or regenerate the missing size. Use the image-generation plugin or WordPress media tools to remove obsolete variants as a set, and check a representative page on desktop and mobile after the cleanup.
Compression helps future growth but does not by itself remove existing files. On WordPress.com, the platform documents that uploaded images and files count toward storage and offers a Storage Add-on. Its documentation also states that Brotli compression applies to CSS, HTML and JavaScript, not to images; enabling Brotli therefore does not reduce the storage occupied by your media library.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRank #4
- No wall warts: Work freely with its bus-powered USB-C. No wall outlet required.
- Big on space: High-capacity storage to store all your files in one place.
- Reliable backup: Safeguard assignments, projects, or sensitive files with trusted performance.
- Fuss-free, clutter-free: One port, one cord, quick connect.
- Peace-of-mind: Comes with two-year limited warranty and Rescue Data Recovery Services.
Remove inactive plugins and themes only after checking dependencies
Inactive does not mean deleted
Deactivating a plugin normally leaves its files and often its database tables in place, so deactivation alone rarely frees meaningful disk space. If the plugin is no longer needed, review its uninstall behavior, export settings that you may need, and remove it through the WordPress Plugins screen or the host’s approved deployment process.
Before removal, check whether a scheduled task, must-use plugin, child theme or custom code calls it. Some extensions store uploads or templates in folders that are not removed automatically. Keep a documented copy of configuration and a rollback package if the plugin is difficult to reinstall.
Keep a safe theme rollback
Delete unused themes only after confirming which theme is active and whether the active theme is a child theme. Keep one known-good fallback theme for recovery, especially when updates are performed through an automated deployment system. A parent theme that appears inactive may still be required by the active child theme.
Clean the database with a measured, reversible plan
A database can accumulate overhead, but there is no single cleanup query that is safe for every WordPress site. Table names, serialized options, custom post types and plugin relationships differ. Export a fresh database backup, record table sizes and remove one class of data at a time.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Common candidates to investigate
- Post revisions: large editorial histories can be reduced after confirming the retention policy your editors need.
- Expired transients: temporary values that have passed their expiration can often be removed; active plugins may recreate them.
- Orphaned metadata: rows left after deleted posts or users may be disposable, but verify that a custom application does not reference them.
- Abandoned plugin tables: remove them only when the plugin is permanently gone and you have a documented restore path.
- Oversized logs stored in tables: identify the plugin producing them and configure retention before purging historical rows.
Run the cleanup in a staging copy when possible. After each class of change, load the front page, representative posts, search, forms, log-in, scheduled jobs and the administrative screens that use the affected plugin. Compare the database size after optimization with the host’s account total; a smaller database may not change the quota if a larger file archive is the real cause.
Compare remedies before choosing one
| Measured source | What to inspect | Typical action | Primary risk | Recovery approach |
|---|---|---|---|---|
| Uploads | Year/month folders, largest originals and generated variants | Remove confirmed-unused files, resize replacements or archive media off-host | Broken image references or missing legal/editorial assets | Restore from an external archive and rebuild references |
| Backup archives | ZIP, TAR and SQL files in the account | Retain the required generations and move older copies off-host | Deleting the only restorable copy | Verify an external copy before removing the hosted one |
| Caches | Plugin and host cache directories | Purge through the owning system and allow regeneration | Temporary performance loss or an interrupted rebuild | Re-enable the cache and let it repopulate |
| Logs | Debug, PHP and plugin logs; newest repeated errors | Rotate or truncate after fixing the source of repetition | Loss of diagnostic evidence while the fault remains | Reproduce the problem with controlled logging |
| Plugins and themes | Inactive extensions, child-theme dependencies and stored data | Uninstall genuinely unused software and retain a fallback theme | Missing code, settings or templates | Reinstall the exact version and restore settings |
| Database | Revisions, transients, orphaned metadata and plugin tables | Clean one verified class at a time after a database export | Broken serialized data or custom integrations | Restore the database and retest on staging |
| Account-level storage | Mail, host backups, other sites and inode usage | Clean the responsible account area or change the storage arrangement | Cleaning the wrong site or violating retention requirements | Use the host’s restore process and an inventory of ownership |
Verify that the cleanup worked
- Wait for host accounting to refresh; some panels update on a schedule rather than instantly.
- Run Site Health’s Directories and Sizes scan again and compare each recorded component with the baseline.
- Refresh the host’s quota report and note the new total, database size and inode count.
- Browse the home page, several media-rich posts, search, forms, user login and the WordPress dashboard.
- Check scheduled tasks, backups, cache regeneration and image uploads. A successful page load does not prove that background jobs still work.
- Keep a change log identifying what was moved, deleted, when, and where its recovery copy is stored.
If a deletion causes an error, restore the smallest affected set first rather than rolling back unrelated work. For a database change, restore the database backup in a staging environment, identify the offending table or rows, and repeat the cleanup with a narrower scope.
Best Value
- USB-C and USB 3.1 compatible.Specific uses: Business, personal
- Innovative style with refined metal cover
- Password protection with 256-bit AES hardware encryption
- Formatted for Mac
When free space does not return
The host number remains high after file cleanup
Recheck host backups, snapshots, mailboxes, logs, staging copies and other sites. Look for a trash or quarantine folder that still counts toward the quota. Ask the host whether deleted files are retained temporarily and whether database backups are counted separately from the live database.
Uploads fail even though gigabytes appear free
Check both disk quota and inode usage. On multisite, inspect the network’s remaining quota and maximum upload size because check_upload_size() can reject a file when either limit is reached. Also check the PHP upload limit and the individual file’s size; increasing a file-size setting will not solve an exhausted account quota.
Recommended Free Tools
The same directory grows again immediately
Identify the process writing to it. A recurring backup job, image optimizer, import, cache warmer or debug error may be recreating files. Disable only the responsible task, preserve evidence needed for diagnosis, correct its retention or logging setting, and then remove the accumulated data.
Choose between off-host archives and more hosted storage
Make the decision using measured size and recovery requirements rather than a guess about what is “too much.” Compare:
- the directory or table that is actually consuming space;
- how many backup generations must remain immediately available;
- whether the host counts backups, logs, email and other sites;
- the cleanup risk and the rollback method;
- the recurring cost and operational effort of external storage versus a larger hosting plan or managed storage add-on.
Off-host archiving is appropriate when old media and backup generations are recoverable but do not need to be served by the website. Additional managed storage is more appropriate when the files are active, access must remain immediate, or the account’s quota includes services you cannot relocate. Keep at least one independently stored, restorable backup whichever option you choose.
Prevent the next storage emergency
- Set an upload policy for maximum practical image dimensions and file formats before editors add media.
- Define how long local backups and logs remain on the account, then automate rotation without deleting the last verified recovery copy.
- Review the largest uploads and database tables monthly, or more often on a high-volume site.
- Delete staging and migration packages after a deployment is verified.
- Monitor both gigabytes and inode count; a site with many tiny cache files can hit the file-count limit first.
- Keep debug logging disabled on production unless diagnosing a specific problem, and set a retention limit when it must remain enabled.
- Test a restore on a schedule. A backup that cannot be opened or restored is not a usable reduction strategy.
The practical rule
Use Site Health to locate WordPress’s large components, the hosting report to account for the entire quota, and a tested backup to make every change reversible. Remove only confirmed-unused media, genuinely abandoned software data, disposable caches and verified database overhead. When the numbers still do not reconcile, investigate the rest of the hosting account before touching more WordPress files.
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.
