On October 17, 2023, the built-in asset optimization feature will be at end of service.
To help smooth the transition, we will be doing a phased approach for this feature removal.
- As of today, July 17, 2023, the feature is deprecated. We’ll show a deprecation notice in the logs for new deploys of affected sites.
- On August 24, 2023, new sites will not be able to use the asset optimization feature.
- On September 19, 2023, we’ll disable mixed content detection and the related GitHub checks.
- On October 17, 2023, the feature will be at end of service. We’ll no longer run asset optimization for new deploys, and any related settings will be removed from the Netlify UI. Any related configuration settings in
netlify.tomlwill be ignored.
Asset optimization is disabled by default. However, if you’re not sure whether your site uses this feature, you can check in a few places:
- Look for the warning icon next to your site name on the Netlify UI.
- Your site configuration. Go to Site configuration > Build & deploy > Post processing > Asset optimization.
netlify.toml. Check for any
- Your deploy logs. The next time you deploy your site, check for a log line that says:
DEPRECATION NOTICE: Your site has asset optimization enabled. This feature will be at end of service on October 17, 2023.
After October 17, 2023, Netlify will still build and serve your site.
However, we won’t run the optimization step on new builds and, as a result, we will serve the original assets. Since asset optimization is just an optimization, all functionality of your site should still work. But, users might experience slower load times because they’ll need to download more and/or bigger files.
For older deploys of sites that had this feature enabled, we’ll keep serving the optimized assets.
You can run a test build without changing your site configuration by creating a branch and updating your
netlify.toml file to include:
[build.processing] skip_processing = true
This way, you can verify the impact on a Deploy Preview or Branch Deploy before merging your changes to your production branch.
Most modern site generators and frontend build tools provide their own way of optimizing assets, so it’s likely that your framework of choice already provides an alternative for this. We recommend you look at their docs and community to find out the recommended option.
We understand that each project has unique requirements, and there isn’t a single solution that will work for everybody. If you have any other questions along the way, let us know!