Netlify integration

Netlify is a hosting platform that builds and deploys your site from Git, with serverless and edge functions and an image CDN. We deploy Astro sites with the official @astrojs/netlify adapter and Next.js sites through Netlify’s zero-config OpenNext adapter. Framer and Webflow host their own sites, so Netlify applies to coded builds.

Updated

Official sources

  1. Next.js on Netlify (opens in a new tab)Netlify docs · docs.netlify.com
  2. Image CDN (opens in a new tab)Netlify docs · docs.netlify.com
  3. @astrojs/netlify (opens in a new tab)Astro docs · docs.astro.build
  4. Astro setup guide (opens in a new tab)Netlify docs · docs.netlify.com
  5. Deploying (opens in a new tab)Next.js docs · nextjs.org
  6. Netlify app (opens in a new tab)Contentful Marketplace · contentful.com

Checked against the official docs on. Tools change often; we re-check before every build.

Press Escape to close.

Netlify integration at a glance
ComplexityLow
Method
  • Framer: Not supported
  • Webflow: Not supported
  • Astro: Native
  • Next.js: Native
Typical setup2 to 4 hours
What we doWe set up the site, domains, build hooks, environment variables per context and deploy previews.
CategoryHosting

Setup by platform

How we set up Netlify

  • Framer

    • Not supported

    Framer hosts Framer sites. Netlify can host a coded part of the project, like docs or an app, on its own subdomain.

  • Webflow

    • Not supported

    Webflow hosts Webflow sites. Netlify comes in when the site, or a part of it, is built in code.

  • Astro

    • Native

    Static Astro sites deploy as they are. @astrojs/netlify adds on-demand rendering, edge middleware, the Netlify Image CDN and sessions on Netlify Blobs.

  • Next.js

    • Native

    Next.js 13.5 and later deploy with zero config through the OpenNext adapter: App Router, ISR, server actions, middleware and next/image via the Image CDN, with a few documented limits.

Use cases

What teams use it for

  1. Static sites with a headless CMS

    Publishing calls a Netlify build hook that rebuilds the site. Contentful has an app for it.

  2. Image transforms on the fly

    The Image CDN resizes and converts to AVIF or WebP, cached at the edge.

  3. Branch previews

    Every pull request gets a deploy preview your team can review and comment on.

Before you add it

What to watch out for

  • Limits

    Next.js edge pages run on Node

    Edge-runtime SSR pages run on Node in your functions region, and rewrites can’t target files in public. We check both before choosing Netlify.

  • Performance

    Build minutes add up

    Rebuilding on every CMS publish is simple, but large sites build slowly. We render high-churn routes on demand instead.

  • Security

    Environment variables per context

    Secrets for production, previews and local development stay separate, so a preview can’t write to live data.

FAQ

Questions about Netlify

Adrian

Can't find your answer?

Book a call and let's talk.

Or email us hello@designme.agency

Do we need to configure anything to run Next.js on Netlify?

No. Netlify applies its OpenNext adapter automatically for Next.js 13.5 and later. Next.js lists Netlify among the platforms working on a verified adapter.

Can Netlify convert images to AVIF or WebP?

Yes. The Netlify Image CDN transforms images with an fm parameter and caches each version at the edge.

Can a Framer or Webflow site run on Netlify?

No, both host their own sites. Netlify fits the coded parts of a project, or the whole site after a move to Astro or Next.js.

You've reached the end, so now…

Tell us what you’re building.

We’ll help you map the right scope, team, timeline, and next steps.

Book a call