Netlify Release Notes

Google’s Gemini 3.6 Flash and Gemini 3.5 Flash-Lite models are now available through Netlify’s AI Gateway and Agent Runners with zero configuration required.

Use the Google GenAI SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the Gemini 3.6 Flash model:

import { GoogleGenAI } from '@google/genai';

export default async () => {
const ai = new GoogleGenAI({});
const response = await ai.models.generateContent({
model: 'gemini-3.6-flash',
contents: 'How can AI improve my coding?',
});
return Response.json(response);
};

Gemini 3.6 Flash and Gemini 3.5 Flash-Lite are available for all Function types and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure.

Learn more in the AI Gateway documentation and Agent Runners documentation.

You can now invite a Developer or Internal Builder to your team without assigning them to an existing project.

Previously, the UI required every new Developer or Internal Builder to be given access to at least one existing project before you could add them. That got in the way of a common workflow: bringing someone on specifically to spin up new work, without handing them the keys to projects they don’t need to touch.

Because both roles can create their own projects directly, this is often exactly what teams want. Invite a new teammate, let them start building right away, and keep your existing projects untouched. When they create a project, they’re automatically assigned the Developer role on it, so they own the work they start without gaining access to everything else.

The result is cleaner, least-privilege onboarding: people get exactly the access they need to begin, and nothing more.

To try it, head to your team’s Members page and invite a Developer or Internal Builder without selecting any existing projects. Learn more about managing project access in our project access docs.

Team Owners on Pro plans can now limit Agent Runners spend for individual members in your team, giving you finer control over how AI credits are used across your team.

Set a single credit limit that applies to every member, then customize it with overrides for specific people who need more (or less) room to work. This makes it easy to give power users a higher ceiling while keeping predictable, budget-friendly defaults for everyone else.

You’ll find these controls in Team Settings under General > AI Enablement.

This builds on our existing team-wide AI usage limits, so you can now manage AI spend both for an entire team and down to each individual member.

We’ve also updated how AI inference credit usage is displayed in your dashboard, making it easier to monitor AI usage and manage your AI spend.

Learn more about AI inference usage and how credits work.

Team Owners on the credit-based Pro plan can now choose how many monthly credits come with their plan, instead of a single fixed amount. Pick the tier that fits your usage, and change it whenever your needs shift.

The new credit tiers, with rollover on higher tiers, can be especially helpful for teams with seasonal surges and teams with consistently high-credit usage and come with some per-credit cost savings.

What’s changing

Previously, every Pro plan included a fixed 3,000 monthly credits for $20/month.

New amounts for monthly credits

Now you can choose from five tiers:

• Monthly credits: 3,000
• Price: $20/mo
• Rollover: No
• Monthly credits: 5,000
• Price: $33/mo
• Rollover: Yes
• Monthly credits: 10,000
• Price: $63/mo
• Rollover: Yes
• Monthly credits: 15,000
• Price: $95/mo
• Rollover: Yes
• Monthly credits: 20,000
• Price: $126/mo
• Rollover: Yes

All tiers include the same Pro plan features: unlimited seats, password protection, and everything else that comes with Pro.

Rollover credits on higher tiers

Choose 5,000 monthly credits or higher and unused credits rollover an additional billing cycle so you get an extra month to use them. The base 3,000-credit tier doesn’t roll over.

Change your tier anytime

Team Owners can switch tiers without limits to how many times they switch. Upgrades take effect immediately with a prorated refund; downgrades take effect next billing cycle. Learn more about switching between Pro tiers.

Learn more

Pro plan

How credits work

Change your pricing plan

Buy credit packs

OpenAI’s GPT-5.6 Sol, Luna, and Terra models are now available through Netlify’s AI Gateway and Agent Runners with zero configuration required.

Use the OpenAI SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the GPT-5.6 Sol model:

import OpenAI from 'openai';

export default async () => {
  const openai = new OpenAI();
  const response = await openai.responses.create({
    model: 'gpt-5.6-sol',
    input: 'Give a concise explanation of how AI works.',
  });
  return Response.json(response);
};

GPT-5.6 Sol, Luna, and Terra are available for all Function types and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure.

Learn more in the AI Gateway documentation and Agent Runners documentation.

New sites created on Netlify now use Node.js 24 by default for both builds and Netlify Functions.

Existing sites aren’t affected — they keep using whatever Node.js version they’re currently pinned to, whether that’s set via a NODE_VERSION environment variable, an .nvmrc/.node-version file, or the engines.node field in package.json.

If you want to move an existing site to Node.js 24, follow the Node.js version configuration guide for builds, and the functions runtime version guide for Netlify Functions.

Google's Gemini 3.1 Flash Lite Image, also known as Nano Banana 2 Lite, is now available through AI Gateway. You can call this lightweight image generation model from Netlify Functions without configuring API keys; the AI Gateway provides the connection to Google for you.

Example usage in a Function:

import { GoogleGenAI } from '@google/genai';
// Netlify Function: Generate an image with Gemini 3.1 Flash Lite Image and return it directly.
// Usage (GET): /.netlify/functions/gemini-31-flash-lite-image?prompt=Your+prompt+here
// Returns: binary image (PNG/JPEG/etc) with proper content-type. If no image, JSON error.
export default async (request: Request) => {
const url = new URL(request.url);
const prompt = url.searchParams.get('prompt') || 'two happy bananas holding flashlights';
const ai = new GoogleGenAI({});
try {
const response = await ai.models.generateContent({
model: 'gemini-3.1-flash-lite-image',
contents: prompt,
config: {
imageConfig: {
aspectRatio: '16:9',
imageSize: '1K'
}
}
});
let imagePart = null;
for (const part of response.candidates[0].content.parts) {
if (part.inlineData) {
imagePart = part.inlineData;
break;
}
}
const bytes = Buffer.from(imagePart.data, 'base64');
const mimeType = imagePart.mimeType || 'image/png';
return new Response(bytes, {
status: 200,
headers: {
'Content-Type': mimeType,
'Cache-Control': 'no-store'
}
});
} catch (err) {
return new Response(JSON.stringify({ error: String(err), prompt }), {
status: 500,
headers: { 'Content-Type': 'application/json' }
});
}
};

Built for speed and lower cost, Flash Lite Image is a good fit for high-volume image generation. It works across any function type and is compatible with other Netlify primitives such as caching and rate limiting, giving you control over request behavior across your site.

Learn more in the AI Gateway documentation.

Anthropic’s Claude Sonnet 5 model is now available through Netlify’s AI Gateway and Agent Runners with zero configuration required.

Use the Anthropic SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the Claude Sonnet 5 model:

import Anthropic from '@anthropic-ai/sdk';

export default async () => {
const anthropic = new Anthropic();
const response = await anthropic.messages.create({
model: 'claude-sonnet-5',
max_tokens: 4096,
messages: [
{
role: 'user',
content: 'How can AI improve my coding?'
}
]
});
return Response.json(response);
};

Claude Sonnet 5 is available for all Function types and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure.

Learn more in the AI Gateway documentation and Agent Runners documentation.

We have redesigned Netlify functions for an improved agent experience.

With these updates, functions are more discoverable, easier to autocomplete, update, and manage for people and agents alike. They move function configuration into code, making it type-safe and immediately visible to editors, tools, and agents, with no platform-specific naming conventions to memorize or get wrong. None of these changes are breaking, so you can adopt them on your own timeline.

Netlify Functions are serverless functions that run on-demand in response to HTTP requests or platform events. They handle server-side logic without any infrastructure to manage, and live in your repository at netlify/functions/.

To learn more about these updates in depth, check out our blog on redesigning Netlify functions for agent experience. See the table below for a summary.

Feature: Event handlers

What changed: Export typed event handlers from the default export object

What it means for agents: Typed handlers are discoverable like any API, with no magic filenames to guess or get wrong.

What you need to do: Nothing required. Adopt the new syntax for new event handlers for better agent discoverability and updates.

Feature: Background functions

What changed: Declare with background: true in config instead of the -background filename suffix

What it means for agents: Type-safe and config-driven, not name-driven. Agents can set it in code without guessing platform naming conventions, and get an error if the value is wrong.

What you need to do: Nothing required. The -background suffix still works.

Feature: Region selection

What changed: Set per-function via the region config property, replacing the global UI setting

What it means for agents: Agents can set region as a type-safe config property, catching invalid values before deploy rather than at runtime. Use deploy previews to test before going live.

What you need to do: Nothing required. Optionally move region out of the UI into config for per-function control.

Feature: Memory and vCPU

What changed: Set via memory or vcpu config properties; both values scale together automatically

What it means for agents: Agents provisioning compute-heavy workloads (inference, large payloads) can do so in code.

What you need to do: Nothing. Defaults unchanged. Set only if your workload needs more than 1 GB / 0.5 vCPU. Requires a credit-based Pro plan.

Feature: getContext()

What changed: Named import from @netlify/functions, replacing the Netlify.context global

What it means for agents: Named imports surface in autocomplete and carry type information. Globals are invisible to agents; named imports are not.

What you need to do: Nothing required. Netlify.context still works. Switch to getContext() for better discoverability.

Learn more in the Netlify Functions documentation, which has also been recently revamped.

What’s new

Astro 7 is out today, and it just works on Netlify on day one. To upgrade, run:

npx @astrojs/upgrade

This will update Astro, the Netlify adapter, and all other official integrations together. You can also check out the official migration guide.

Some highlights include:

• Vite 8 — Astro 7 upgrades to Vite 8, bringing faster builds and improved dev tooling.
• Sätteri is now the default markdown processor — Astro’s new native markdown pipeline replaces remark/rehype as the default. If your project uses remark or rehype plugins, you’ll need to install @astrojs/markdown-remark separately to keep them working.
• Advanced routing is stable — Previously behind an experimental flag, advanced routing is now enabled by default. The default entry point has moved from src/app.ts to src/fetch.ts.
• Streaming rendering is stable — The streaming-based rendering engine is now the default, replacing the legacy queued approach.
• Background dev server for AI coding agents — astro dev now detects AI coding environments and runs as a background process automatically. New astro dev stop, astro dev status, and astro dev logs commands let you manage it directly.
• Astro DB is deprecated — The astro db, astro login, astro logout, astro link, and astro init CLI commands have been removed. Switch to a dedicated database client.
• Custom logger is stable — context.logger is now always available in API routes and middleware, with built-in json, node, and console handlers.

Check the full upgrade guide for all the details.

Watch out for the new markdown defaults

If your site uses remark or rehype plugins, you’ll need to take action before upgrading. In Astro 7, the default markdown pipeline is Sätteri — Astro’s own native processor. The remark/rehype pipeline is no longer included by default.

To keep your existing plugins working, install the remark package separately:

npm install @astrojs/markdown-remark

Once installed, your existing markdown.remarkPlugins, markdown.rehypePlugins, and markdown.remarkRehype config options will continue to work as before. If you’re not using any remark or rehype plugins, no changes are needed — Sätteri handles standard Markdown out of the box.

Deploy an Astro 7 site on Netlify

If you want to get started with a new site, start with the Astro on Netlify doc, or just click this button:

Deploy to Netlify

React Router 8 was just released and is already supported on Netlify.

The breaking changes are largely limited to these new minimums:

• Node.js 22.22.0+
• React 19.2.7+
• Vite 7+

How to upgrade

To upgrade your existing Netlify project follow the React Router 8 upgrade guide and upgrade the Netlify React Router Vite plugin to v4.0.0+:

npm i @netlify/vite-plugin-react-router@latest

Try it now

To deploy a brand new, React Router 8 application to Netlify, click this button:

Deploy to Netlify

What you get

Full framework feature support, serverless and edge functions included, plus full Netlify platform emulation in local dev for you and your agents.

React Router on Netlify

@netlify/vite-plugin-react-router release notes

You can now use as many environment variables as your Serverless Functions need. The 4KB total size limit on environment variables no longer applies to functions running on the current Netlify Functions runtime.

This limit was a common source of friction. Teams with several API keys, connection strings, or feature flags could quietly bump into the cap and see their functions fail to deploy or run, often with confusing errors. With the limit gone, you no longer have to ration space or work around the ceiling for the configuration your functions legitimately need.

The limit still applies to functions running in Lambda compatibility mode. If your functions are using Lambda compatibility mode and you want to remove the size limit entirely, consider upgrading to the current Netlify Functions runtime.

Learn more about environment variables in Netlify Functions in our documentation.