Roku Channel content delivery and avails submission guide
close
See what Molten Cloud can do for you
Thank you!
Something went wrong. Please try again or reach out contact@moltencloud.com
Your privacy is important to us. We won't share your information, as stated in our privacy policy.
Festivals
Industry Insight
Cinema
Marché du Film

Delivering Content to Roku Channel — Avails, Specs, and Workflow

Platform Delivery Guide

Delivering Content to Roku Channel

Avails format, Direct Publisher feed structure, technical specifications, and delivery workflow for the device-native FAST/AVOD platform pre-installed on 80M+ Roku devices.

Roku Channel is the device-native FAST and AVOD platform built directly into every Roku device — giving it a reach of more than 80 million active accounts without requiring users to download a separate app. For independent distributors, Roku Channel offers one of the most accessible major platform delivery models: a Direct Publisher feed system (JSON or MRSS), a standard rev-share AVOD deal structure similar to Tubi, and a growing international footprint across the US, UK, Canada, Mexico, and Germany. Molten Cloud, the rights management and royalties platform for film and television, automates Roku Channel avails generation, manages Direct Publisher feed metadata from verified rights data, and tracks ad-revenue royalties across every territory where content is distributed.

Roku Channel — Platform Snapshot
80M+
Active Roku Accounts
5
Countries Available
100%
Free / AVOD-FAST Model
0$
User Subscription Cost

Key FactsKey Facts: Delivering to Roku Channel

  • Roku Channel operates as a device-native FAST and AVOD platform — pre-installed on every Roku streaming device and Roku TV. Unlike channel apps in the Roku Channel Store (which users must install), Roku Channel content is surfaced directly in the home screen experience, giving it structural distribution advantages over third-party FAST channels on the same platform.
  • Roku uses Direct Publisher for metadata and feed delivery, a self-service content management system that accepts catalog feeds in JSON or MRSS format. Distributors maintain a hosted feed that Roku ingests automatically — metadata updates, new titles, and window changes are reflected when the feed updates, reducing manual re-delivery friction compared to platforms requiring asset re-upload.
  • The deal structure is rev-share AVOD — similar to Tubi and Pluto TV. Content is free to viewers, revenue is generated from advertising, and distributors earn a percentage based on viewership. Licensing is typically non-exclusive, making Roku Channel stackable with other AVOD and FAST platforms simultaneously.

Content ProfileWhat Roku Channel Acquires and How Deals Work

Roku Channel's content strategy spans broad genres with particular strength in movies, TV series, news, and lifestyle content. The platform benefits from Roku's scale as a device ecosystem — content that performs well on Roku Channel reaches a massive installed base across multiple screen types.

Roku Channel — Content & Deal Profile
AspectDetails
Revenue ModelAVOD rev-share — distributor earns percentage of ad revenue based on content viewership hours
Deal StructureNon-exclusive licensing (typically 1-3 year terms) — content can be on other AVOD/FAST platforms simultaneously
Content PreferencesMovies, TV series (all genres), documentary, news, lifestyle, reality, classic films, family content
TerritoriesUS (primary), UK, Canada, Mexico, Germany — international expansion ongoing
Minimum CatalogNo strict minimum; larger catalogs preferred for direct deals — smaller catalogs via aggregators or Direct Publisher
ExclusivityNon-exclusive — Roku Channel rarely requires exclusive rights, making it stackable with Tubi, Pluto TV, and other AVOD/FAST services

The non-exclusive, rev-share model makes Roku Channel a natural complement to other AVOD platforms. Distributors regularly license the same titles to Roku Channel, Tubi, Pluto TV, and Freevee simultaneously — maximizing ad-revenue across platforms from the same underlying rights without territorial exclusivity conflicts.

Avails FormatRoku Channel Avails Requirements

Roku Channel avails submission follows a content proposal and review process before Direct Publisher onboarding. Once approved, distributors maintain a JSON or MRSS feed that serves as the ongoing avails and metadata source for the platform.

Roku Channel Avails — Key Fields
FieldDescriptionNotes
TitleExact title as it should appear on platformMust match metadata feed and artwork exactly
Content Typemovie, series, episode, shortFormVideoSeries require season and episode structure in feed
TerritoryAvailable countries for licensingRoku Channel operates in 5 countries — specify each separately
License Start / EndAvailability window dates in ISO 8601 formatWindows reflected in Direct Publisher feed automatically
GenrePrimary and secondary genre using Roku taxonomyMust use Roku's genre values — custom labels cause feed rejection
Content RatingMPAA or TV rating per territoryRequired for parental controls; TV-MA and R-rated accepted
Language / CaptionsOriginal audio language + available caption tracksEnglish captions required for US distribution of non-English content
Rights ConfirmationDistributor confirms AVOD/FAST rights for each territoryRoku verifies against rights claims — conflicts delay or block ingestion

Technical SpecsVideo, Audio, and Caption Requirements

Roku Channel's technical specifications are intentionally standard, accepting H.264 in MP4 containers — the same accessible profile used by Tubi and other AVOD platforms. This reduces transcoding complexity compared to premium platforms like Netflix or Apple TV+ that require MXF or proprietary packaging.

Roku Channel Technical Specifications
SpecificationRequirement
Video CodecH.264 (AVC) — high profile
ContainerMP4 (preferred) or MOV
Resolution1920 × 1080 (HD) — minimum 1280 × 720
Frame Rate23.976, 24, 25, or 29.97 fps (constant frame rate required)
Video Bitrate8-20 Mbps for HD (higher preferred)
Audio CodecAAC or AC-3 (Dolby Digital)
Audio ChannelsStereo (2.0) or 5.1 surround
Audio Bitrate192+ kbps (stereo) / 384+ kbps (5.1)
CaptionsSRT or WebVTT — English required for non-English US content
Artwork16:9 landscape (1920×1080 min) + 2:3 portrait (800×1200 min)
Feed FormatJSON (Roku Content Feed spec) or MRSS — hosted at a stable public URL

DeliveryHow Content Gets to Roku Channel

Roku Channel delivery uses a feed-driven model distinct from upload-based platforms. The core workflow combines a content proposal, Direct Publisher feed setup, and ongoing automated ingestion.

Content Proposal
Submit catalog overview to Roku's content partnerships team. Include title list, genres, available territories, and performance data from other platforms if available.
Title Selection & Deal Agreement
Roku reviews and selects titles for the channel. Deal terms (rev-share percentage, window length, territories) are finalized in a content licensing agreement.
Direct Publisher Feed Setup
Create and host a JSON or MRSS feed conforming to Roku's Content Feed specification. The feed contains all metadata, availability windows, video URLs, artwork URLs, and caption file URLs for licensed titles.
Asset Hosting & Feed Submission
Host video files (MP4), caption files (SRT/VTT), and artwork at publicly accessible URLs. Submit the feed URL to Roku via the Direct Publisher portal or Content Partner portal for initial ingestion review.
QC & Ingestion
Roku runs technical QC against the feed and assets. Turnaround is typically 5-10 business days. Feed errors or asset rejections require corrections and feed re-submission.
Go Live & Ongoing Feed Updates
Content goes live on Roku Channel. Subsequently, metadata changes, new titles, and expiring windows are managed by updating the hosted feed — Roku re-ingests on a scheduled crawl cycle without requiring manual re-delivery.

PitfallsCommon Mistakes When Delivering to Roku Channel

Top 5 Delivery Pitfalls

1. AVOD/FAST rights not confirmed per territory. Roku Channel requires AVOD and FAST distribution rights for each territory in the feed. Distributors who submit titles without verifying per-territory AVOD rights face ingestion blocks and rights conflict notices from Roku.

2. Feed URL instability. Roku's Direct Publisher crawls a hosted feed URL on a regular schedule. If the feed URL changes, goes offline, or returns errors between crawl cycles, content can be removed from the channel without warning. A stable, always-available feed URL is a production requirement, not an optional detail.

3. Using incorrect genre values. Roku's Content Feed specification requires genre values from Roku's defined taxonomy. Submitting custom genre labels or values from other platform taxonomies (e.g., Tubi's genre list) causes feed validation failures.

4. Missing or malformed availability windows. License start and end dates in the feed must be in ISO 8601 format. Missing end dates or incorrect date formatting causes Roku to either reject the feed entry or ingest content without proper expiration handling — leading to content remaining live after license expiry.

5. Variable frame rate video. Roku Channel requires constant frame rate (CFR). Variable frame rate (VFR) content — common from consumer-grade encoders and screen-capture tools — triggers QC failure and asset rejection.

ComparisonManual Delivery vs. Molten Cloud

Manual Process
1-2 days
Per submission cycle (30 titles)
  • Check AVOD/FAST rights per territory manually from contracts
  • Build and maintain Direct Publisher JSON feed by hand
  • Track ad-revenue royalties in separate spreadsheets
  • Monitor license expiration dates and update feed manually
With Molten Cloud
1-2 hours
Per submission cycle (30 titles)
  • AVOD/FAST availability query: instant, from verified rights data
  • Generate Roku Direct Publisher-formatted feed in one click
  • AVOD revenue ingestion and royalty calculation automated
  • Automated license expiration alerts and feed window updates (90, 60, 30 days)

AutomationHow Molten Cloud Automates Roku Channel Delivery

Molten Cloud connects rights data directly to Roku Channel's feed-driven delivery workflow:

  • AVOD/FAST-specific avails generation. Molten Cloud queries the rights database for AVOD and FAST availability per territory — filtering out titles where only SVOD or TVOD rights exist. The generated avails and feed entries contain only titles with confirmed rights for each Roku Channel territory.
  • Direct Publisher feed generation. Molten Cloud generates a Roku Content Feed-compliant JSON feed from verified rights and metadata — including availability windows, genre taxonomy values, caption file references, and artwork URLs. The feed is maintained automatically as rights data changes, eliminating manual feed editing.
  • Ad-revenue royalty tracking. Roku Channel's AVOD rev-share model produces variable monthly revenue per title. Molten Cloud ingests Roku revenue reports, maps them to titles and territories, and calculates participant royalties automatically — no manual spreadsheet reconciliation required.
  • Cross-platform AVOD stacking. Because Roku Channel's deals are non-exclusive, the same content typically runs on multiple AVOD/FAST platforms simultaneously. Molten Cloud manages avails, feed delivery, and royalties across Roku Channel, Tubi, Pluto TV, and other AVOD services from the same rights database — ensuring consistent territorial tracking across all platforms.

Frequently Asked Questions

How do distributors deliver content to Roku Channel?

Distributors deliver content to Roku Channel through a feed-driven process: a content proposal is submitted to Roku's content partnerships team for title selection and deal agreement; approved titles are then delivered via a JSON or MRSS feed (conforming to Roku's Content Feed specification) hosted at a stable public URL. Video assets (H.264 in MP4, 1080p), caption files (SRT/VTT), and artwork are hosted at URLs referenced in the feed. Roku ingests the feed via Direct Publisher on a scheduled crawl cycle, meaning metadata updates and new titles are reflected automatically without manual re-upload. Roku Channel operates a 100% AVOD/FAST model with non-exclusive licensing, and distributors earn ad-revenue share. Molten Cloud automates avails generation, Direct Publisher feed creation, and ad-revenue royalty tracking from verified rights data.

What are Roku Channel's technical delivery requirements?

Roku Channel requires video in H.264 codec within MP4 containers at minimum 1280×720 resolution (1920×1080 preferred), with constant frame rate (23.976, 24, 25, or 29.97 fps). Audio must be AAC or AC-3 in stereo or 5.1 surround at 192+ kbps (stereo) or 384+ kbps (5.1). Caption files must be in SRT or WebVTT format — English captions are required for non-English content distributed in the US. Artwork requires a 16:9 format (1920×1080 minimum) and 2:3 portrait (800×1200 minimum). The distinguishing characteristic of Roku Channel delivery is the feed format: metadata and asset references are submitted via a JSON or MRSS Content Feed hosted at a stable URL, rather than via direct file upload to a portal.

Is Roku Channel non-exclusive for content licensing?

Yes. Roku Channel typically licenses content on a non-exclusive basis, meaning distributors can make the same titles available on other AVOD and FAST platforms simultaneously — Tubi, Pluto TV, Freevee, and others. This non-exclusive model makes Roku Channel an ideal platform for distributors maximizing ad-supported revenue across multiple services from the same catalog. License terms are typically 1-3 years with revenue-share compensation based on viewership-driven ad revenue. Molten Cloud manages non-exclusive AVOD/FAST licensing across multiple platforms from a single rights database, tracking territorial availability consistently and preventing rights conflicts across simultaneous platform deals.

How does Molten Cloud help with Roku Channel content delivery?

Molten Cloud automates Roku Channel delivery through four core capabilities: AVOD/FAST-specific avails generation (one-click export of titles with confirmed rights per Roku territory), Direct Publisher feed generation (automated JSON Content Feed creation from rights and metadata data, maintained as windows change), ad-revenue royalty tracking (automated ingestion of Roku revenue reports with per-title, per-territory royalty calculations), and license window monitoring (automated alerts before Roku license expirations at 90, 60, and 30 days, with feed window updates applied automatically). Because Roku Channel is non-exclusive, Molten Cloud simultaneously manages the same content's avails, feeds, and royalties across other AVOD/FAST platforms — all from the same verified rights data, eliminating duplicated work across parallel platform relationships.

Molten Cloud generates Roku Channel-ready avails and Direct Publisher feeds from your rights data, and tracks ad-revenue royalties automatically — across Roku Channel and every other AVOD platform.

See how AVOD delivery works in Molten Cloud