R2 for Assets
This is a member-only chapter. Log in with your Signal Over Noise membership email to continue.
Log in to readModule 5 · Section 4 of 5
R2 for Assets
For both deployment paths, large assets (images, fonts, downloadable files) are better served from a CDN than from your site’s own hosting.
All eight of my sites use Cloudflare R2 for this. Assets live at assets.jimchristian.net — served from R2 with a cache rule that sets Cache-Control: max-age=31536000, immutable on images. They load fast and don’t count against VPS bandwidth.
The pattern: upload assets to R2, reference them by their CDN URL in your Markdown and components, never commit large binary files to the repository.
R2 has a generous free tier (10 GB storage, zero egress fees). It’s the first thing I’d set up for any site with more than a handful of images.