Overview
Contentful is the market-leading headless content management system (CMS), used by development teams to manage and deliver structured content via API. Over 30% of Fortune 500 companies use Contentful to power websites, mobile apps, and digital experiences. Contentful decouples content authoring from content delivery — content editors manage entries in Contentful's Studio, and developers query content via REST or GraphQL APIs at build time or runtime.
What This Script Does
In production websites, Contentful typically has no client-side script footprint — content is fetched server-side or at build time, resulting in pre-rendered HTML delivered to the browser. Client-side Contentful scripts appear in specific scenarios: preview environments, Live Preview for editors, and the optional Contentful App Framework for embedded custom tools.
Contentful Live Preview SDK
@contentful/live-previewnpm package — Injected into staging and preview environments to enable real-time content editing. Approximately 50–100KB.- Establishes a
postMessageconnection between the Contentful Studio interface and the preview page, enabling inline editing where editors can click on content to edit it in place. - No tracking cookies are set by Live Preview. All communication is between the Contentful Studio tab and the preview page.
Contentful Content Preview API
- Client-side requests to
preview.contentful.com/spaces/{spaceId}/entries/— The Preview API returns draft content (unpublished changes) for preview environments. - Authentication via a Preview API key (typically embedded in preview environment variables, not production).
- Preview API keys grant read-only access to draft content and should never be exposed in production builds.
Contentful Images API
images.ctfassets.net— Contentful's image transformation and delivery CDN (backed by Cloudflare). No cookies set.downloads.ctfassets.net— Asset download CDN.videos.ctfassets.net— Video asset CDN.
Production Delivery API
- Content Delivery API (CDA):
cdn.contentful.com/spaces/{spaceId}/entries/— In production server-side rendering (Next.js, Nuxt, etc.), this API call happens on the server, not in the browser. No client-side cookies or JavaScript footprint. - GraphQL API:
graphql.contentful.com/content/v1/spaces/{spaceId}— Same: server-side only in production.
No Cookies Set in Production Contentful does not set any cookies on visitor browsers in a production website deployment. All content delivery is API-based (server-side) or CDN-based (static assets). No tracking, analytics, or session management cookies originate from Contentful in production.
Consent & Compliance
Consent category: Functional
- GDPR/ePrivacy: No cookies are set in production by Contentful. No personal data about website visitors is processed by Contentful's delivery infrastructure — the delivery APIs are called server-side. The Images CDN (
images.ctfassets.net) delivers assets without setting cookies. No consent is required for Contentful in production deployments. - Preview environments: Contentful Live Preview is used only by authenticated editors in controlled preview environments, not by end users. No public-facing consent obligations arise from preview tools.
- CCPA/CPRA: No personal information about website visitors is processed by Contentful in production. Contentful processes content editor data (Contentful Studio user accounts) under its own privacy policy, not as a processor for the website visitor.
- EU data residency: Contentful offers EU data residency (spaces hosted in EU data centers). Content Delivery API requests from EU visitors can be routed to EU infrastructure.
Should You Block This Without Consent?
No. In production, Contentful has no client-side scripts to block — content delivery is entirely server-side or via CDN asset URLs. No cookies are set on visitor browsers. There is nothing to block, and attempting to block ctfassets.net would break image and asset delivery. In preview environments, Live Preview scripts serve an internal editorial purpose with no visitor-facing privacy implications.
Is Contentful GDPR compliant?
Contentful typically loads functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Contentful can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Contentful, not on Contentful itself.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
Contentful's trackers are occasionally seen, seen on under 1% of the sites ConsentStack has scanned. Scan your own site to see which of these are firing before consent.
ctfassets.netEssentialctfassets.net is an essential domain operated by Contentful, used to keep the site working, including security, load balancing, and sessions. Seen on under 1% of scanned sites.
Frequently Asked Questions
Related Vendors


Manage consent for Contentful
ConsentStack automatically detects and manages Contentful trackers so your site stays compliant with global privacy regulations.