CF Image proxy

Image proxy and CDN for Cloudflare Workers.

Features

• Free 💪
• Super simple to setup and self-host
• Perfect lighthouse scores
• Handles CORS for you
• Normalizes origin URLs
• Respects pragma: no-cache and related headers
• Used in hundreds of prod sites

Setup

1. Create a new blank Cloudflare Worker.
2. Fork / clone this repo
3. Update the missing values in wrangler.toml
4. npm install
5. npm run dev to test locally
6. npm run deploy to deploy to cloudflare workers 💪

wrangler.toml

name = "cf-image-proxy"
type = "javascript"
webpack_config = "webpack.config.js"
account_id = "TODO"
workers_dev = true

[env.production]
zone_id = "TODO"
route = "TODO"

You can find your account_id and zone_id in your Cloudflare Workers settings.

Your route should look like "exampledomain.com/*".

Cloudflare Polish

You can optionally enable Polish in your Cloudflare zone settings if you want to enable on-the-fly image optimization as part of your CDN. In many cases, this will serve images to supported clients in an optimized webp format.

This may increase costs, so it's not recommended for everyone. The CF worker should support both configurations without issue.

CDN

By default, all assets will be served with a cache-control header set to public, immutable, s-maxage=31536000, max-age=31536000, stale-while-revalidate=60, which effectively makes them cached at all levels indefinitely (or more practically until Cloudflare or your browser purges the asset from its cache).

If you want to change this cache-control header or add additional headers, see src/fetch-request.js.

Usage

Next.js Notion Starter Kit

If you're using this image proxy as part of nextjs-notion-starter-kit, all you need to do is set imageCDNHost in your site.config.js and your image proxy will be used automatically.

If you're not using this Next.js Notion boilerplate, then read on.

General Usage

In the application where you want to consume your proxied images, you'll need to replace your third-party image URLs.

You can replace them with your proxy domain plus a path that contains the URI-encoded version of your original domain. In TypeScript, this looks like the following:

const imageCDNHost = 'https://exampledomain.com'

export const mapImageUrl = (imageUrl: string) => {
  if (imageUrl.startsWith('data:')) {
    return imageUrl
  }

  if (imageCDNHost) {
    // Our proxy uses Cloudflare's global CDN to cache these image assets
    return `${imageCDNHost}/${encodeURIComponent(imageUrl)}`
  } else {
    return imageUrl
  }
}

Technical Notes

A few notes about the implementation:

• It is hosted via Cloudflare (CF) edge workers.
• It is transpiled by webpack before uploading to CF.
• CF runs our worker via V8 directly in an environment mimicking web workers.
• This means that our worker does not have access to Node.js primitives such as fs, dns and http.
• It does have access to a custom web fetch API.

TODO

• [x] Initial release extracted from Notion2Site
• [ ] Support restricting the origin domain in order to prevent abuse
• [ ] Add a snazzy demo

License

MIT © Travis Fischer

Support my OSS work by following me on twitter