Molten Cloud platform delivery guide
No items found.

Plex Delivery Guide — Avails, Specs & Workflow (With a Note on Crackle)

Plex Delivery Guide

Avails format, technical specifications, metadata requirements, and delivery workflow for one of the few AVOD platforms with true global reach. Plus a note on why Crackle is no longer a viable delivery target.

A note on Crackle. This post was originally published covering both Crackle and Plex. In June 2024, Crackle's parent company Chicken Soup for the Soul Entertainment filed for Chapter 11 bankruptcy, which was converted to Chapter 7 liquidation in July 2024. Crackle's consumer website went offline on June 7, 2025, and the Crackle trademark and assets were auctioned in April 2025. As of April 2026, there is no operational Crackle distribution pipeline accepting new content from distributors. If you landed here searching for Crackle delivery specs, the short answer is, Crackle is not a current delivery target. The post below focuses on Plex, which remains an active and growing AVOD platform with a distributor-friendly intake process and the widest geographic reach of any free streaming service.

Plex is one of the most geographically expansive free ad-supported streaming services in the market, serving 25 million monthly active users across more than 240 countries and territories, with a growing catalog of 45,000+ on-demand titles and 1,500+ FAST channels (per the January 2026 Plex Rewind report). Unlike Tubi, Pluto TV, or The Roku Channel, all of which are US-first with limited international expansion, Plex has operated with a global-by-default model since its AVOD launch. For distributors holding broad territorial rights, this makes Plex one of the few single-deal paths to worldwide AVOD distribution.

Delivering content to Plex runs through the Plex Partner Portal, which manages avails intake, metadata matching, master uploads, and royalty reporting. Because Plex originated as a personal media server platform, its metadata standards are unusually precise, accurate EIDR or IMDb identifiers are essential for correct database matching, and ingestion delays almost always trace back to missing or ambiguous identifiers. Molten Cloud, the rights management and royalties platform for film and television, automates Plex avails generation with populated EIDR/IMDb identifiers, manages AVOD royalty ingestion from Plex revenue reports, and ensures every title submitted is backed by verified territorial AVOD rights data, so distributors avoid both ingestion delays and rights exposure.

Plex, Platform Snapshot
25M+
Monthly Active Users
240+
Countries & Territories
45K+
AVOD Titles
1,500+
FAST Channels

Key FactsKey Facts: Delivering to Plex

  • Plex operates a global AVOD service serving 25M monthly active users across 240+ countries and territories, making it one of the few AVOD platforms where a single deal can cover worldwide distribution.
  • Non-exclusive licensing is standard. Content licensed to Plex can run simultaneously on Tubi, Pluto TV, The Roku Channel, and other AVOD services, this non-exclusive stacking is how AVOD distribution scales ad revenue across the ecosystem.
  • Metadata precision is the single biggest ingestion blocker. Plex's database-matching relies on universal content identifiers. Submitting avails without EIDR or IMDb IDs causes delays while Plex manually resolves matches.
  • Delivery is handled through the Plex Partner Portal, which manages avails intake, master uploads, and royalty reporting. Plex is generally receptive to a broad range of titles relative to more curated platforms.
  • Revenue is AVOD rev-share, per-title monthly payouts based on ad impressions served against each title. Royalty reports are delivered through the Partner Portal on a recurring monthly cadence.

AvailsPlex Avails: Territory, Window, and Rights

Plex avails follow a standard AVOD template, each row defines a title-territory-window combination with rights confirmation, parental rating, and content identifiers. Because Plex is global, a single title distributed worldwide produces a compact avails file using region-level or country-level rows rather than per-country duplication (Plex accepts both; region-level is preferred where rights align).

Plex Avails Template, Key Fields
FieldDescriptionCommon Errors
Title IDMust match Plex database, EIDR or IMDb ID strongly recommendedMissing identifiers cause manual-match delays
TerritoryPlex is global, specify each country or region (ISO 3166-1)Vague 'worldwide' entries rejected, use explicit territory codes
Window Start / EndISO 8601 dates; Plex accepts flexible windows, no strict minimum termOpen-ended windows without renewal logic
Content RatingMPAA / TV rating; Plex enforces parental controls based on ratingInaccurate or missing ratings block parental-control compliance
Rights TypeNon-exclusive AVOD rights requiredSubmitting SVOD- or TVOD-only content fails rights verification
Genre / LanguageStandard genre taxonomy; primary audio language codeIncorrect genre tags reduce discoverability in Plex's catalog

Technical SpecsPlex Technical Specifications

Plex accepts standard H.264/MP4 delivery at 1080p, the most widely supported codec and container combination in the AVOD ecosystem. Distributors who have already prepared masters for Tubi, Pluto TV, or The Roku Channel can generally deliver to Plex without re-transcoding.

Plex Delivery Specs
SpecRequirement
Video CodecH.264 (AVC), High Profile, Level 4.0 or higher
ContainerMP4 (preferred); MOV accepted for ProRes masters
Resolution1080p (1920×1080), progressive scan
Bitrate8–10 Mbps CBR or VBR; higher accepted for premium tiers
AudioAAC-LC, 2.0 stereo minimum; 5.1 accepted where source supports
CaptionsSRT or WebVTT sidecar, English required; additional languages encouraged for territory reach
ArtworkKey art 16:9 (1920×1080) and portrait 2:3 (2000×3000), PNG or high-quality JPEG

WorkflowDelivery Workflow, Plex

Plex's Partner Portal has a relatively self-service structure compared to curated acquisition services, qualifying distributors can submit catalogs directly without the lengthy proposal process required at platforms like Netflix or Peacock.

  • Step 1 — Apply for Partner Portal access. Complete the Plex distributor application with a catalog overview and confirmation of non-exclusive AVOD rights.
  • Step 2 — Submit avails. Upload the avails template with title-territory-window rows, EIDR or IMDb IDs populated, and rights type confirmed per title.
  • Step 3 — Upload masters. Deliver H.264/MP4 masters (or ProRes for remastering) through the Portal's ingest endpoint, paired with sidecar captions and artwork.
  • Step 4 — Metadata matching. Plex's catalog team matches your submissions against their database using the identifiers provided, missing or ambiguous identifiers trigger manual review.
  • Step 5 — QC and publish. Plex runs technical QC (codec, audio loudness, caption timing) and parental-control validation; passing titles publish to the catalog on the window start date.
  • Step 6 — Royalty reporting. Monthly per-title AVOD revenue reports are delivered through the Partner Portal, with ad-impression and revenue data per territory.

MistakesCommon Mistakes When Delivering to Plex

Top Delivery Pitfalls for Plex
  • Missing EIDR or IMDb IDs. Plex's database matching relies on universal content identifiers. Submitting avails without them causes ingestion delays while Plex's team manually resolves metadata matches.
  • Submitting without confirmed AVOD rights. Distributors who hold only SVOD or TVOD rights cannot legally deliver to ad-supported platforms. Rights verification will fail and the submission will be rejected.
  • Vague territory entries. 'Worldwide' without explicit ISO 3166-1 country codes gets rejected, Plex's global distribution requires precise territory rows.
  • Inaccurate content ratings. Plex enforces parental controls based on MPAA / TV ratings at the platform level, submitting inaccurate ratings blocks compliance and can delay publish.
  • Not stacking across parallel AVOD platforms. Because Plex is non-exclusive, the same content should run simultaneously on Tubi, Pluto TV, and The Roku Channel, failing to deliver in parallel leaves ad-revenue on the table from titles already prepared for AVOD.

Manual vs. MoltenManual Delivery vs. Molten Cloud

Manual Plex Delivery
  • Check AVOD rights availability per title and territory manually from contract PDFs
  • Look up EIDR and IMDb IDs per title by hand before avails submission
  • Reformat avails rows into Plex's template structure
  • Track royalty reports in spreadsheets, reconciling per-title impressions with underlying rights
  • Repeat the entire process per parallel AVOD platform (Tubi, Pluto, Roku)
Molten Cloud
  • AVOD availability query, instant, from verified rights data
  • EIDR and IMDb IDs populated when you generate Plex avails
  • Plex-formatted avails exported in a few minutes
  • AVOD revenue ingestion and royalty calculation automated
  • Same rights data powers parallel AVOD delivery to Tubi, Pluto TV, Roku Channel, no duplicate data entry

How It WorksHow Molten Cloud Automates Plex Delivery

Plex's distributor-friendly intake is a double-edged sword, it lowers the barrier to entry, but it also means many distributors end up managing Plex alongside 4-5 parallel AVOD services from spreadsheets, duplicating rights checks and royalty reconciliation at every step. Molten Cloud connects rights data to the Plex delivery workflow, and to every other AVOD platform in the stack, from a single source of truth:

  • AVOD-specific avails generation. Molten Cloud queries the rights database for AVOD availability, filtering out titles where only SVOD or TVOD rights exist. The generated avails file for Plex contains only titles with confirmed AVOD rights for each territory.
  • EIDR and IMDb ID management. When you regenerate Plex avails, identifiers are populated from the rights database in a few minutes, eliminating the manual lookup step that causes most ingestion delays.
  • AVOD royalty tracking. Plex produces variable monthly ad-revenue reports per title. Molten Cloud ingests these reports automatically, calculating per-title royalty allocations against underlying contracts without manual reconciliation.
  • Parallel AVOD orchestration. Because Plex is non-exclusive, Molten Cloud manages the same content's avails and royalties across parallel AVOD platforms, Tubi, Pluto TV, The Roku Channel, all from the same verified rights data, eliminating the duplication that manual multi-platform management requires.

FAQFrequently Asked Questions

How do distributors deliver content to Plex?

Distributors deliver content to Plex through the Plex Partner Portal, which manages content intake for Plex's AVOD streaming catalog (separate from Plex's personal media server functionality). Qualifying distributors submit an application, then upload avails (title-territory-window rows with EIDR or IMDb IDs), H.264/MP4 masters at 1080p with SRT/WebVTT captions, and artwork through the Portal. Plex's catalog team matches submissions against their database using the provided identifiers, runs technical QC, and publishes passing titles on the window start date. Plex distributes to 240+ countries and territories, making it one of the few AVOD platforms with true global reach from a single deal.

What happened to Crackle, and is it still possible to deliver content there?

Crackle is no longer an active delivery target. Crackle's parent company, Chicken Soup for the Soul Entertainment, filed for Chapter 11 bankruptcy in late June 2024, which was converted to Chapter 7 liquidation on July 10, 2024. Crackle's consumer website went offline on June 7, 2025, and the Crackle trademarks and assets were auctioned on April 23, 2025. As of April 2026, there is no operational Crackle distributor pipeline. Distributors previously delivering to Crackle should redirect catalog efforts toward other AVOD platforms, Plex, Tubi, Pluto TV, and The Roku Channel all operate non-exclusive licensing models that accept the same content in parallel.

Can I deliver the same content to Plex and other AVOD services simultaneously?

Yes, Plex operates a non-exclusive licensing model, meaning the same titles can run simultaneously on Tubi, Pluto TV, The Roku Channel, and other AVOD / FAST services. This non-exclusive stacking is standard practice in AVOD distribution and is how distributors maximize ad-revenue across the ecosystem from a single set of rights. The key requirement is confirming that AVOD rights are held for each relevant territory, Plex distributes to 240+ countries and territories, so broad territorial AVOD rights unlock the widest geographic reach. Molten Cloud manages non-exclusive AVOD licensing across all platforms from a single rights database, ensuring territorial availability is tracked consistently without duplicate data entry.

How does Molten Cloud help with Plex content delivery?

Molten Cloud automates Plex delivery through AVOD-specific avails generation (quick export with confirmed AVOD rights per territory), EIDR and IMDb ID population at regeneration time to prevent ingestion delays, and automated ad-revenue royalty tracking against underlying contracts. Because Plex is non-exclusive, Molten Cloud also manages the same content's avails and royalties across parallel AVOD platforms, Tubi, Pluto TV, The Roku Channel, all from the same verified rights data, eliminating the duplication that manual multi-platform management requires.

Molten Cloud generates Plex-ready avails from your rights data and tracks AVOD royalties automatically, across Plex and every other AVOD service in your stack.

See how AVOD delivery works in Molten Cloud
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.