Video Embeds in Contentful: Workflows and Delivery

or JavaScript players. No adaptive bitrate streaming or video transcoding is supported. Large videos may affect loading time and performance. Method 2: Embedding Videos from External Platforms For enhanced playback control, streaming, and analytics, Contentful recommends embedding videos from external platforms such as YouTube, Vimeo, or enterprise video providers. Options: Short Text Field: Store the embed URL (e.g., https://www.youtube.com/embed/...) in a string field. Rich Text Field with Embedded Entry: Embed a video component as a linked entry using the EmbeddedEntryBlock. Example: Rich Text Embed Structure {'nodeType': 'embedded-entry-block','content': [],'data': {'target': {'sys': {'type': 'Link','linkType': 'Entry','id': 'entry_id'}}}} Explanation: This structure represents an embedded entry block in a Rich Text field, linking to another Contentful entry by its ID. The nodeType defines it as a block, and the data.target.sys.id holds the reference to the actual entry to be rendered in the frontend. Frontend Handling: Render embeds using conditional logic based on the contentType or use custom components for different providers. Contentful does not automatically render embeds—developers must handle this in the frontend. Comparison table summarizing the two methods Video Asset Delivery via Contentful CDN When videos are uploaded to Contentful, they are served as static files through Contentful’s global CDN. Each file receives a permanent, public URL that can be embedded in applications or websites. Example URL format: https://images.ctfassets.net/{space_id}/{asset_id}/{filename}.mp4 This approach ensures global caching and fast delivery, but it comes with specific limitations: No media optimization : Videos are not transcoded or resized. The original file is served as-is, with no support for adaptive streaming or multiple resolutions. No fallback support : There’s no automatic format switching (e.g., from MP4 to WebM) for browser compatibility. Limited security : URLs are public and do not support signing or token-based expiration. Any user with the link can access the file. Access control must be manual : To restrict access, developers must implement logic at the application layer or proxy requests through a secured backend. This method is suitable for lightweight or non-sensitive video content where performance and access control are not critical requirements. For more advanced needs, consider using a dedicated video delivery service. Best Practices Use external video platforms if adaptive streaming, subtitles, analytics, or custom playback control is required. Use Contentful-hosted videos only for small, non-critical media files without high performance or streaming requirements. Store video metadata (duration, dimensions, platform ID) in dedicated fields for structured frontend rendering.

Boost Campaign Performance Through Video