If your excluded files are not downloaded yet, the exclusions feature is likely working as designed—but it can take time to show the expected result. This is most common on sites with large or high-churn folders inside wp-content/uploads/.
Two things drive this behavior:
- Infinite Uploads processes sync work through Action Scheduler (a background job queue).
- Exclusions can only be applied after the initial sync has completed, not before.
Because of this, your media may not have returned to a non-cloud URL while the scheduled actions finish running and the system reconciles file state.
Symptoms
You might be seeing one or more of the following:
- You add an exclusion, but your file URL is still pointing to Infinite Uploads
- Excluding a large directory seems to “do nothing” for a long time.
Why this happens
1) Infinite Uploads uses Action Scheduler (jobs run in the background)
Infinite Uploads relies on Action Scheduler to process large workloads in batches. This keeps operations stable on typical WordPress hosting, but it also means:
- Work is queued in advance.
- Changing settings does not instantly process everything.
- Your host’s scheduler speed directly affects how fast changes “take effect.”
2) Exclusions can trigger “download/reconcile” work
When you exclude a directory after it has been managed by Infinite Uploads, the system may need to restore local copies of those files before it stops managing them. This prevents your site from ending up in a state where:
- WordPress expects a file locally, but
- Infinite Uploads is no longer managing that path
If the excluded directory is large, this “download/reconcile” phase can take time, especially when processed via Action Scheduler.
3) You can’t set exclusions before the initial sync
Exclusions are not a pre-sync “ignore list.” The intended workflow is:
- Complete the initial sync.
- Then apply exclusions to remove specific paths from ongoing management.
If you try to exclude folders before the initial sync is complete, you won’t get the behavior you expect.
4) Default exclusions already exist
Infinite Uploads includes default exclusions for common non-media patterns. Custom exclusions are in addition to these defaults, and are most useful when your site has unique cache/log/temp folders inside uploads/.
Expected behavior (what “working” looks like)
After you save exclusions:
- You may see activity related to excluded paths in the media library as the system finishes queued work and/or reconciles local files.
- Over time, excluded folders should stop being treated as cloud-managed media going forward.
What affects how long it takes
The “settling” time depends mostly on:
- Folder size (number of files matters as much as total GB)
- How quickly Action Scheduler runs on your host
- How many tasks were already queued
- Site traffic and cron reliability (low traffic sites often process queued jobs more slowly)
What you can do
1) Let the queue finish
If you excluded a large directory, it may simply need time to process the queued actions and any reconciliation work.
2) Make sure Action Scheduler can run reliably
If your site’s cron is unreliable or isn’t firing, Action Scheduler jobs may run slowly or sporadically. Ensuring WP-Cron is functioning properly (or using a real server cron if your host supports it) can dramatically improve progress.
3) Avoid excluding real Media Library folders unless you mean it
Only exclude paths that truly should not be part of your media workflow (cache/log/temp output). Excluding real media directories can lead to confusion later, especially if you’ve freed up local storage and some items are cloud-only.