CDN for Contentful
A delivery edge in front of the Contentful stack.
Contentful stores content; the public experience still needs a CDN for the front end, transformed imagery and any cacheable API or SSR output you own.
Put Cloud CDN in front of the website or application origin that reads Contentful. Cache HTML, assets and public images. Purge when Contentful webhooks fire.
Why teams use Aptranet
What CDN for Contentful looks like on this network.
Cloud CDN caches and accelerates eligible content on 210+ points of presence, with Origin Shield when the origin must stay out of the way.
Front ends close to readers
Next.js, Remix or static sites that consume Contentful are cached on 210+ PoPs.
Asset transformation at the edge
Adapt Contentful images for each layout without baking every size into the CMS.
Webhook-driven purge
Invalidate pages when Contentful publishes so editors are not waiting on TTL.
How to set it up
A cutover you can validate before DNS moves.
Create the Cloud CDN configuration, prove it on an Aptranet hostname, then point production DNS when the path looks correct.
- 1Front the experience origin
Connect the website or SSR app that calls Contentful, not the Contentful web app.
- 2Cache pages and assets
Use long TTLs for hashed assets and purgeable TTLs for HTML.
- 3Hook purge to Contentful
On publish webhooks, purge the URLs that embed the changed entries.
- 4Map the public hostname
Attach certificates and cut over DNS after a successful test.
Outcomes
What changes once the hostname is on Aptranet.
- Contentful-powered sites are delivered from the edge
- Publish can purge without a full rebuild wait
- Images can be adapted per page
- The Contentful web app stays off the public cache
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
You can still use Contentful assets as the origin. Cloud CDN caches and can further transform what you deliver on your hostname.
Usually cache the front end. Caching the Delivery API is optional and must exclude preview and draft tokens.
Preview hostnames or draft tokens must bypass cache so editors see unpublished changes.
Yes. Static or incrementally regenerated pages still benefit from a global edge and purge.