Lighter files for your business

Yes. Once the plugin is active, Spark picks up your existing media. You don't need to re-upload or process anything manually.

You'll get a notice around 80% and when you hit 100%. After that, processing waits until your limit resets or you choose a larger plan.

We work with secure copies and account for rollback. So if you want, you can go back to the old state.

That depends on your plan. On the Agency plan you can work with lots of sites at once without hassle. Unsure? Just email and we'll think it through with you.

WordPress multisite is set up differently by many hosting and plugin combinations. In many cases Spark works just like on single-site installs, but do check your setup or ask us.

For web display, some metadata is often unnecessary and heavy. Spark can strip it where it's safe for your use case; specific needs can be discussed and adjusted.

Yes, as long as cache rules are correct. After a bulk run, a cache purge may be needed so visitors see the new formats. Common WordPress cache plugins are compatible if you don't set aggressive "ignore query string" on media.

You set the policy as Spark supports it: often AVIF where possible, WebP as a broad fallback, original as a last resort. Details are in the plugin settings.

Yes, you can often choose to optimize only new media, only the library, or both. This allows you to migrate gradually.

Double optimization is rarely needed. Compare results on bytes and quality; Spark focuses on perceptual quality and modern codecs in your own workflow.

That depends on the number of assets, average size, and your limit. Small sites often finish quickly; large libraries process gradually through the queue.

Yes, you can stop processing or deactivate the plugin. Keep in mind: visitors will see your old delivery again until you come back.

Lossless: no quality loss, less byte savings. Lossy: maximum savings, higher risk of visible artifacts if you push too far. Glossy sits in between and is often the sweet spot for web shops and marketing visuals.

Spark is built around modern image delivery on the web. How your theme handles srcset varies by theme/builder; the plugin integrates where possible.

Sometimes, but conflicts can arise (double conversion or double lazy-load). Test on staging and keep one "source of truth" for compression.

Media keeps evolving; video and vector are on our roadmap. Let us know if you're handling volumes now.

Smaller images mainly help LCP and overall load time. It's not a guarantee for green scores - server, JS, and fonts matter too.

Caching, old HTML, or a plugin forcing the old file. Check response headers, cache layers, and whether your theme actually serves the optimized file.