Completely disabling post-processing of deploys

Does anyone know how to completely disable post-processing on Netlify?

Non of the post-processing settings are enabled in my dashboard. However each deploy still has ~2min of post-processing:

I’d like my deploys to be even faster, so tips are welcome!

Note: maybe the checks for “mixed content” and parsing of “header rules” and “redirect rules” are part of post-processing? Since my deploy has a lot of pages (~800) I can imagine the mixed content check may take some time. However I would prefer another CI to check this part with something like Lighthouse CI.

Two things you can’t control in postprocessing:

  1. form detection. We can disable this for you as long as you have optimization totally disabled (I see you do), AND you don’t want to use our forms service. If this is true, let me know your site’s API ID and I can turn off forms processing for you.

  2. mixed content warnings. We look for http:// links in your pages and tell you about those so you’ll be aware that a browser is likely to act ugly when displaying the pages. No way to disable this.

However, we wouldn’t have to process at all if you used best practices in creating your site. I don’t think you just edited 839 pages in one commit, yet you have 839 new assets to upload. This is likely due to some antipattern you use in building, as described in this article:

If you don’t change most files, we don’t have to upload and scan most files (no processing of files that didn’t change will occur), so that’s the “best way” to speed up your deploys :slight_smile:

1 Like

Hi Chris, thanks for the fast reply!

I’d love it if you could turn off form processing for our project with this App ID 846d57cb-c5ef-452b-9f3b-c2c43365617d. We are not using Netlify forms for that project.

Of course you are totally right about your point of changing as little files as possible. I can try and explain why we have so many changes:
We have different events triggering our deploys: git push, datocms publish, nightly cron job. In development many code changes, like changing the site header, affect all our HTML pages. And our project has a lot of HTML pages: 833 out of those 839 are HTML pages. The HTML pages contain a static list of locations with opening hours for the next 7 days. The nightly cron job fetches all the new opening hours and that again affects all HTML pages. Only on a cms publish event can we generate specific HTML pages.
We do use an immutable cache strategy for all our assets (configured in _headers) for better UX, but clearly we can’t do that for our HTML.

It is our suggestion that you abstract out the things that could change every page, such as changeable filenames and headers, newsflashes, and list of store opening hours so they reside in one file, that is included from your other files/normal pages. Then you don’t have to upload all the unchanged content of the 833 pages…

Anyway, I’ve disabled that form processing on that site so your next deploy should activate that setting.

I’m not sure how to abstract all things out. A big part of my love for Netlify and the JAMstack is that every page starts and works for everyone with just plain markup. Everything that requires JavaScript (and APIs) I see as an enhancement. So for very dynamic and nice-to-have content I can imagine loading that in asynchronously and thus not affecting the initial page markup. For something like our opening hours we could consider that. However components that are part of the core navigation such as the header, I want to work regardless of the capabilities of the client consuming our website. So I will always want to include that in the static page markup.

Before we started using Netlify we had our own CI and hosting of static generated files using an Nginx server. We would use Server Side Includes (SSI) to include things like headers to abstract them out of our static page markup (<!--# include file="header.html" -->). I see a thread on SSI on Netlify from which I understand Netlify has no such mechanism. Is that correct, or any plans maybe? (Sorry if this gets off-topic, I could start a new thread).

Thanks for disabling form processing on our project. I’ll mark your original answer as solution.

1 Like


Server Site Includes sounds like a function of server-side rendering. While that is similar to JAMstack, it still assumes you will be processing your pages before it is served so it’s not identical. As mentioned in that other community thread, we server non-server processed pages. That said, SSI seems like it’s outside the scope of JAMstack.

Hope that helps.

With the form-processing disabled our post processing times are down from ~2min to ~5sec (even with a large number of new files):


If I want to do the same for other projects, is there a way I can do this through the Netlify Open API? I wasn’t able to find it yet.

Is the reason form-processing is on by default so that developers don’t have to enable anything manually and it just works out-of-the-box? Personally I would like to be able to control this as a developer, either via the Netlify app or a netlify.toml setting.

1 Like

Hmmmm… personally I like that suggestion. The idea of being able to explicitly opt-out of the post-processing which looks for forms to handle could give a nice deployment speed bump to people who fully understand this and know for sure that they don’t need it. Especially useful for those who also have very many pages in their site.