Skip to main content
Knowledge

Staging first, then live

Test compression profiles on staging before running a full library on production.

Workflow

No export needed: same plugin on clone, different license/slot per plan.

Why you shouldn't start directly on production

Testing a compression setting on your live site means any errors are immediately visible to visitors, and you have no reference point to easily compare before and after. On staging, you can try out, compare, and adjust a profile at your own pace, without risk to your actual site's visitors.

Step-by-step plan: safely from staging to live

Set up a current staging copy

Work with a clone of your site that is representative of the current situation, including a realistic media library.

Test your compression profile on a sample

First process a limited, representative selection of images on staging instead of immediately processing your entire library.

Compare the result visually and in terms of file size

Check whether the quality meets your standards and how much file size you actually gain.

Adjust the profile if needed

If the result is too aggressive or too conservative, adjust the profile and repeat the test on staging.

Roll out the setting to production

Once you're satisfied, use the same setting on live, preferably outside peak hours and with a recent backup at hand.

Staging and licenses: what changes

A brief summary of what happens in each situation:
SituationWhat happensImportant note
Staging as a separate copy (clone)You use the same plugin on the clone; a separate media export is not needed.Make sure the clone is representative of your current media library.
License or slot per environmentStaging and live typically count as separate environments on your license, depending on your plan.Check your plan to see how many environments or sites are included.
After a successful testYou manually apply the tested setting to production; staging and live remain separate environments.Schedule the production rollout intentionally, preferably outside peak hours.

Common mistakes when moving from staging to live

  • Letting the same media library process actively on both staging and live, which is confusing and creates duplicate work.
  • Fine-tuning a setting on staging but forgetting to actually apply it to live.
  • Leaving staging running permanently as an extra environment without your team knowing about it.
  • Not clearing the cache after the final rollout to live, so visitors still see old files.

Frequently asked questions

No. You use the same plugin on the clone; a separate media export is not needed. However, you typically use a different license or a different slot, depending on your plan.

Staging typically counts as a separate environment with its own license or slot. Check your plan for exact details, as this can vary by situation.

You can run them side by side as long as you're clear about which environment uses which setting. If you mix them up, you risk doing double work or testing a setting you never actually deploy to live.

That depends on your plan; usually you'll need a separate slot or environment for this. Check your license settings or contact us if you're unsure.

Test on a staging environment that mirrors your live setup, including a comparable media library and the same hosting conditions where possible. This gives you the best chance that the results will match.

Yes, check a sample of pages and clear your cache so visitors see the new, optimized files instead of an old, cached version.