@astrojs/ cloudflare

This adapter allows Astro to deploy your on-demand rendered routes to Cloudflare.

If you’re using Astro as a static site builder, you don’t need an adapter to deploy to Cloudflare.

Learn how to deploy your Astro site in our Cloudflare deployment guide.

Why Astro Cloudflare

Section titled Why Astro Cloudflare

Cloudflare’s Developer Platform lets you develop full-stack applications with access to resources such as storage and AI, all deployed to a global edge network. This adapter builds your Astro project for deployment through Cloudflare.

Installation

Section titled Installation

Astro includes an astro add command to automate the setup of official integrations. If you prefer, you can install integrations manually instead.

Add the Cloudflare adapter to enable SSR in your Astro project with the astro add command. This will install @astrojs/cloudflare and make the appropriate changes to your astro.config.mjs file in one step.

npm

npx astro add cloudflare

pnpm

pnpm astro add cloudflare

Yarn

yarn astro add cloudflare

Manual Install

Section titled Manual Install

First, add the @astrojs/cloudflare adapter to your project’s dependencies using your preferred package manager.

npm

npm install @astrojs/cloudflare

pnpm

pnpm add @astrojs/cloudflare

Yarn

yarn add @astrojs/cloudflare

Then, add the adapter and your desired on-demand rendering mode to your astro.config.mjs file:

astro.config.mjs

import { defineConfig } from 'astro/config';
import cloudflare from '@astrojs/cloudflare';

export default defineConfig({
  output: 'server',
  adapter: cloudflare(),
});

Options

Section titled Options

The Cloudflare adapter accepts the following options:

cloudflareModules

Section titled cloudflareModules

Type: boolean
Default: true

Enables imports of .wasm, .bin, and .txt modules.

This functionality is enabled by default. If you’d like to disable, set cloudflareModules to false.

imageService

Section titled imageService

Type: 'passthrough' | 'cloudflare' | 'compile' | 'custom'
Default: 'compile'

Determines which image service is used by the adapter. The adapter will default to compile mode when an incompatible image service is configured. Otherwise, it will use the globally configured image service:

• cloudflare: Uses the Cloudflare Image Resizing service.
• passthrough: Uses the existing noop service.
• compile: Uses Astro’s default service (sharp), but only on pre-rendered routes at build time. During SSR for pages rendered on-demand, all astro:assets features are disabled.
• custom: Always uses the image service configured in Image Options. This option will not check to see whether the configured image service works in Cloudflare’s workerd runtime.

astro.config.mjs

import { defineConfig } from "astro/config";
import cloudflare from '@astrojs/cloudflare';

export default defineConfig({
  adapter: cloudflare({
     imageService: 'cloudflare'
  }),
  output: 'server'
})

platformProxy

Section titled platformProxy

Determines whether and how the Cloudflare runtime is added to astro dev. It contains proxies to local workerd bindings and emulations of Cloudflare specific values, allowing the emulation of the runtime in the Node.js dev process. Read more about the Cloudflare Runtime.

Note

Proxies provided by this are a best effort emulation of the real production. Although they are designed to be as close as possible to the real thing, there might be a slight differences and inconsistencies between the two.

platformProxy.enabled

Section titled platformProxy.enabled

Type: boolean
Default: true

Determines whether to enable the Cloudflare runtime in development mode.

platformProxy.configPath

Section titled platformProxy.configPath

Type: string
Default: undefined

Defines the path to the Wrangler configuration file. If no value is set, it tracks wrangler.toml, wrangler.json, and wrangler.jsonc in the project root.

platformProxy.environment

Section titled platformProxy.environment

Type: string
Default: undefined

Sets the Cloudflare environment to use. You must select an environment defined in the Wrangler configuration file, otherwise an error occurs.

platformProxy.persist

Section titled platformProxy.persist

Type: boolean | { path: string }
Default: true

Sets whether and where to save binding data locally to the file system.

• If set to true, binding data is stored in .wrangler/state/v3/. It is the same as the default setting for wrangler.
• If set to false, binding data is not stored in file system.
• If set to { path: string }, binding data is stored in the specified path.

Note

wrangler’s --persist-to option adds a sub directory called v3 under the hood while the @astrojs/cloudflare persist property does not. For example, to reuse the same location as running wrangler dev --persist-to ./my-directory, you must specify: persist: { path: "./my-directory/v3" }.

The following configuration shows an example of enabling the Cloudflare runtime when running the development server, as well as using a wrangler.json config file. It also specifies a custom location for persisting data to the filesystem:

import cloudflare from '@astrojs/cloudflare';
import { defineConfig } from 'astro/config';

export default defineConfig({
  adapter: cloudflare({
    platformProxy: {
      enabled: true,
      configPath: 'wrangler.json',
      persist: {
        path: './.cache/wrangler/v3'
      },
    },
  }),
});

routes.extend

Section titled routes.extend

On Cloudflare Workers, this option is not applicable. Refer to Routing on Cloudflare Workers for more information.

On Cloudflare Pages, this option allows you to add or exclude custom patterns (e.g. /fonts/*) to the generated _routes.json file that determines which routes are generated on-demand. This can be useful if you need to add route patterns which cannot be automatically generated, or exclude prerendered routes.

More information about the custom route patterns can be found in Cloudflare’s routing docs. Any routes specified are not automatically deduplicated and will be appended to the existing routes as is.

routes.extend.include

Section titled routes.extend.include

Type: { pattern: string }[]
Default: undefined

Configures additional routes to be generated on demand by the Cloudflare adapter in the routes.extend.include array.

routes.extend.exclude

Section titled routes.extend.exclude

Type: { pattern: string }[]
Default: undefined

Configures routes to be excluded from on-demand rendering in the routes.extend.exclude array. These routes will be prerendered and served statically instead, and will not invoke the SSR function. Additionally you can use this option to serve any static asset (e.g. images, fonts, css, js, html, txt, json, etc.) files directly without routing the request through the SSR function.

astro.config.mjs

export default defineConfig({
  adapter: cloudflare({
    routes: {
      extend: {
        include: [{ pattern: '/static' }], // Routes a prerended page to the SSR function for on-demand rendering
        exclude: [{ pattern: '/pagefind/*' }], // Use Starlight's pagefind search, which is generated statically at build time
      }
    },
  }),
});

sessionKVBindingName

Section titled sessionKVBindingName

Type: string
Default: SESSION

Added in: astro@5.6.0

The sessionKVBindingName option allows you to specify the name of the KV binding used for session storage. By default, this is set to SESSION, but you can change it to match your own KV binding name. See Sessions for more information.

astro.config.mjs

export default defineConfig({
  adapter: cloudflare({
    sessionKVBindingName: 'MY_SESSION_BINDING',
  }),
});

Cloudflare runtime

Section titled Cloudflare runtime

Usage

Section titled Usage

The Cloudflare runtime gives you access to environment variables and bindings to Cloudflare resources. The Cloudflare runtime uses bindings found in the wrangler.toml/wrangler.json configuration file.

You can access the bindings from Astro.locals.runtime:

src/pages/index.astro

---
const { env } = Astro.locals.runtime;
---

You can access the runtime from API endpoints through context.locals:

src/pages/api/someFile.js

export function GET(context) {
  const runtime = context.locals.runtime;

  return new Response('Some body');
}

See the list of all supported bindings in the Cloudflare documentation.

Environment variables and secrets

Section titled Environment variables and secrets

The Cloudflare runtime treats environment variables as a type of binding.

For example, you can define an environment variable in wrangler.json as follows:

wrangler.json

{
  "vars" : {
    "MY_VARIABLE": "test"
  }
}

Secrets are a special type of environment variable that allow you to attach encrypted text values to your Worker. They need to be defined differently to ensure they are not visible after you set them.

To define secrets, add them through the Wrangler CLI rather than in your Wrangler config file.

npx wrangler secret put <KEY>

To set secrets for local development, you also need to add a .dev.vars file to the root of the Astro project:

.dev.vars

DB_PASSWORD=myPassword

You can then access environment variables, including secrets, from the env object available from Astro.locals.runtime:

src/pages/index.astro

---
const { env } = Astro.locals.runtime;
const myVariable = env.MY_VARIABLE;
const secret = env.DB_PASSWORD;
---

Cloudflare environment variables and secrets are compatible with the astro:env API.

Typing

Section titled Typing

wrangler provides a types command to generate TypeScript types for the bindings. This allows you to type locals without the need to manually type them. Refer to the Cloudflare documentation for more information.

Every time you change your configuration files (e.g. wrangler.toml, .dev.vars) you need to run wrangler types.

Note

You can create a pnpm script to run wrangler types automatically before other commands.

package.json

{
  "scripts": {
    "dev": "wrangler types && astro dev",
    "start": "wrangler types && astro dev",
    "build": "wrangler types && astro check && astro build",
    "preview": "wrangler types && astro preview",
    "astro": "astro"
  }
}

You can type the runtime object using Runtime:

src/env.d.ts

type Runtime = import('@astrojs/cloudflare').Runtime<Env>;

declare namespace App {
  interface Locals extends Runtime {
    otherLocals: {
      test: string;
    };
  }
}

Cloudflare Platform

Section titled Cloudflare Platform

Headers

Section titled Headers

You can attach custom headers to your responses by adding a _headers file in your Astro project’s public/ folder. This file will be copied to your build output directory.

This is available on Cloudflare Workers and Pages.

Assets

Section titled Assets

Assets built by Astro are all named with a hash and therefore can be given long cache headers. By default, Astro on Cloudflare will add such a header for these files.

Redirects

Section titled Redirects

You can declare custom redirects to redirect requests to a different URL. To do so, add a _redirects file in your Astro project’s public/ folder. This file will be copied to your build output directory.

This is available on Cloudflare Workers and Pages.

Routes

Section titled Routes

Routing on Cloudflare Workers

Section titled Routing on Cloudflare Workers

Routing for static assets is based on the file structure in the build directory (e.g. ./dist). If no match is found, this will fall back to the Worker for SSR. Read more about static asset routing with Cloudflare Workers.

Unlike Cloudflare Pages, with Workers, you do not need a _routes.json file.

Currently, the Cloudflare adapter always generates this file. To work around this, create a .assetsignore file in your public/ folder, and add the following lines to it:

public/.assetsignore

_worker.js
_routes.json

Routing on Cloudflare Pages

Section titled Routing on Cloudflare Pages

For Cloudflare Pages, routing uses a _routes.json file to determine which requests are routed to the server function and which are served as static assets. By default, a _routes.json file will be automatically generated for your project based on its files and configuration.

You can specify additional routing patterns to follow in your adapter config, or create your own custom _routes.json file to fully override the automatic generation.

Creating a custom public/_routes.json will override the automatic generation. See Cloudflare’s documentation on creating a custom _routes.json for more details.

Sessions

Section titled Sessions

The Astro Sessions API allows you to easily store user data between requests. This can be used for things like user data and preferences, shopping carts, and authentication credentials. Unlike cookie storage, there are no size limits on the data, and it can be restored on different devices.

Astro automatically configures Workers KV for session storage when using the Cloudflare adapter. Before using sessions, you need to create a KV namespace to store the data and configure a KV binding in your Wrangler config file. By default, Astro expects the KV binding to be named SESSION, but you can choose a different name if you prefer by setting the sessionKVBindingName option in the adapter config.

1. Create a KV namespace using the Wrangler CLI and make note of the ID of the new namespace:

   npx wrangler kv namespace create "SESSION"

2. Declare the KV namespace in your Wrangler config, setting the namespace ID to the one returned by the previous command:

   wrangler.json

   wrangler.json

   {
     "kv_namespaces": [
       {
         "binding": "SESSION",
         "id": "<KV_NAMESPACE_ID>"
       }
     ]
   }

   wrangler.toml

   wrangler.toml

   kv_namespaces = [
     { binding = "SESSION", id = "<KV_NAMESPACE_ID>" }
   ]

3. You can then use sessions in your server code:

   src/components/CartButton.astro

   ---
   export const prerender = false;
   const cart = await Astro.session?.get('cart');
   ---
   
   <a href="/checkout">🛒 {cart?.length ?? 0} items</a>

Note

Writes to Cloudflare KV are eventually consistent between regions. This means that changes are available immediately within the same region but may take up to 60 seconds to propagate globally. This won’t affect most users as they are unlikely to switch regions between requests, but it may be a consideration for some use cases, such as VPN users.

Cloudflare Module Imports

Section titled Cloudflare Module Imports

The Cloudflare workerd runtime supports imports of some non-standard module types. Most additional file types are also available in Astro:

• .wasm or .wasm?module: exports a WebAssembly.Module that can then be instantiated
• .bin: exports an ArrayBuffer of the raw binary contents of the file
• .txt: exports a string of the file contents

All module types export a single default value. Modules can be imported both from server-side rendered pages, or from prerendered pages for static site generation.

The following is an example of importing a Wasm module that then responds to requests by adding the request’s number parameters together.

pages/add/[a]/[b].js

// Import the WebAssembly module
import mod from '../util/add.wasm';

// Instantiate first in order to use it
const addModule: any = new WebAssembly.Instance(mod);

export async function GET(context) {
  const a = Number.parseInt(context.params.a);
  const b = Number.parseInt(context.params.b);
  return new Response(`${addModule.exports.add(a, b)}`);
}

While this example is trivial, Wasm can be used to accelerate computationally intensive operations which do not involve significant I/O such as embedding an image processing library, or embedding a small pre-indexed database for search over a read-only dataset.

Node.js compatibility

Section titled Node.js compatibility

Out of the box, Cloudflare does not support the Node.js runtime APIs. With some configuration, Cloudflare does support a subset of the Node.js runtime APIs. You can find supported Node.js runtime APIs in Cloudflare’s documentation.

To use these APIs, your page or endpoint must be server-side rendered (not pre-rendered) and must use the import {} from 'node:*' import syntax.

pages/api/endpoint.js

export const prerender = false;
import { Buffer } from 'node:buffer';

You’ll also need to modify the vite configuration in your Astro config to allow for the node:* import syntax:

astro.config.mjs

import { defineConfig } from "astro/config";
import cloudflare from '@astrojs/cloudflare';

export default defineConfig({
  adapter: cloudflare({}),
  output: 'server',
  vite: {
    ssr: {
      external: ['node:buffer'],
    },
  },
})

Additionally, you’ll need to follow Cloudflare’s documentation on how to enable support. For detailed guidance, please refer to the Cloudflare documentation on enabling Node.js compatibility.

Package Compatibility Implications

If a project imports a package into the server that uses the Node.js runtime APIs, this can cause issues when deploying to Cloudflare. This issue arises with package that do not use the node:* import syntax. It is recommended that you contact the authors of the package to determine if the package supports the above import syntax. If the package does not support this, you may need to use a different package.

Preview with Wrangler

Section titled Preview with Wrangler

To use wrangler to run your application locally, update the preview script.

For Workers:

package.json

"preview": "wrangler dev ./dist"

For Pages:

package.json

"preview": "wrangler pages dev ./dist"

Developing with wrangler gives you access to Cloudflare bindings, environment variables, and the cf object. Getting hot reloading of the Astro dev server to work with Wrangler might require custom setup. See community examples.

Meaningful error messages

Section titled Meaningful error messages

Currently, errors during running your application in Wrangler are not very useful, due to the minification of your code. For better debugging, you can add vite.build.minify = false setting to your astro.config.mjs.

astro.config.mjs

export default defineConfig({
  adapter: cloudflare(),
  output: 'server',
  vite: {
    build: {
      minify: false,
    },
  },
});

More integrations

Front-end frameworks

• 

  @astrojs/alpinejs

• 

  @astrojs/preact

• 

  @astrojs/react

• 

  @astrojs/solid⁠-⁠js

• 

  @astrojs/svelte

• 

  @astrojs/vue

SSR adapters

• 

  @astrojs/cloudflare

• 

  @astrojs/netlify

• 

  @astrojs/node

• 

  @astrojs/vercel

Other integrations

• 

  @astrojs/db

• 

  @astrojs/mdx

• 

  @astrojs/markdoc

• 

  @astrojs/partytown

• 

  @astrojs/sitemap