Video infrastructure built for developers
Mux was founded in 2015 by Jon Dahl, Steve Heffernan, Matt McClure and Adam Brown to build video infrastructure for developers. The founding team brought experience from Zencoder and Video.js. Dahl, Heffernan and a third co-founder had started Zencoder in 2010 before its acquisition by Brightcove in 2012, giving the team a background in cloud encoding and web video players.
The service is provided by Mux, Inc., based in San Francisco, United States. The company combines remote work with offices in San Francisco, New York and London. Its APIs and developer components bring encoding, storage, live and on-demand delivery, and playback analytics into applications built by its customers.
Mux has received backing from investors including Coatue, Accel, Andreessen Horowitz and Y Combinator, and announced a Series D round in 2021. Its product range has expanded into players, video understanding and AI workflows. Today, Mux Robots supports video analysis and processing, while the Vercel Marketplace integration connects Mux to frontend application deployment workflows.
One API for uploads, encoding and playback
Mux Video can ingest a downloadable file or accept uploads directly from your users. It processes video into adaptive HLS streams, while playback URLs, SDKs and webhooks connect the workflow to your application. Thumbnails, GIFs, timeline previews, multiple audio tracks and captions sit alongside the same video asset, making it useful for courses, subscription content, creator tools and user-generated video.
On-demand assets use Basic, Plus or Premium quality. Basic has free encoding and a reduced bitrate ladder; Plus adjusts encoding to the content, while Premium targets more demanding picture-quality requirements. All three support up to 4K on demand, but live streaming and DRM require Plus or Premium. Storage and delivery remain separate charges, with resolution and quality affecting the bill. Mux does not retain an exact copy of the uploaded source file, so keep a separate original if you need one.
Multi-CDN delivery and live streaming
Mux selects a CDN when a viewer starts playback and delivers video through multiple networks. To handle a CDN failure during an active session, enable redundant streams and use a compatible player. With ordinary playback, the application may need to restart a failed session before Mux selects another CDN. Validate the player, retry behavior and networks your audience actually uses before launch.
Live streams accept RTMP, RTMPS or SRT, play through HLS and can become on-demand recordings automatically. Low-latency mode uses LL-HLS and benefits from a stable broadcast connection. Mux describes latency as low as about five seconds, depending on the player, viewer location and network; allow for that delay when designing interactions. Streams disconnect after 12 hours by default, so discuss longer broadcasts with support in advance.
Analytics, content protection and AI workflows
Mux Data measures playback startup, failures, buffering, quality and engagement, helping teams investigate differences across devices, regions, players and CDNs. Data analytics for Mux Video playback are included. Teams using another video delivery service can also buy Data independently, choosing a plan by view volume. Adding playback analytics and migrating video delivery are separate decisions.
For new web players, Mux recommends Video.js with its maintained video, audio and Data components. Mux Player for Web is in maintenance mode; existing integrations should plan updates around the migration guidance. Mobile players have separate SDKs. Paid or members-only content can use playback tokens issued by your server, with domain and User-Agent restrictions. Widevine, PlayReady and FairPlay DRM require enablement, and Apple playback needs your own FairPlay certificate. Screen-capture and output protection vary by device.
Mux Robots runs managed workflows for summaries, chapters, moderation, captions and translation. Directives can coordinate jobs automatically after an upload. Workflows have prerequisites for captions, audio, asset state and language: assets must be ready and no longer live, and DRM-only playback IDs are unsupported. With the open-source @mux/ai toolkit, your team instead manages the application runtime, model accounts and model-provider costs.
Integrations and operational history
Mux integrates with Sanity upload and preview workflows and is available through the Vercel Marketplace. Digital agency Raket also names Mux in its Fractal Design website implementation. Teams can plan around their existing content systems and application frameworks, then validate playback on target devices and the resulting costs.
In its November 13, 2026 update, Mux confirmed that some historical views were missing for EU collection customers between June 17 and November 5, and that missing views older than seven days could not be recovered. Real-time metrics and alerting were unaffected by that incident. A separate October 28 incident disrupted video playback and ingest; the closure update noted that some on-demand assets created around the incident still needed processing. Confirm video recovery procedures and analytics retention and export separately.
Plans, usage and purchasing terms
Mux Video bills input, storage and delivery separately, using duration and resolution with second-level measurement. Basic on-demand input is free; live streaming requires Plus or Premium and supports up to 1080p. Pay as you go includes a USD 20 monthly usage credit, while Launch and Scale exchange a monthly prepayment for a larger credit. Usage beyond the credit remains billable. Standalone Mux Data charges by monitored views; basic monitoring of Mux-hosted video is included with Video.
Free is an ongoing on-demand plan that requires no card, with a 10-video library limit and monthly delivery and Robots allowances. It is not a timed trial of every paid feature. Check paid-plan and activation requirements before using live streaming, a larger library or add-ons.
Self-service paid accounts can use a credit or debit card, or a US bank account eligible for ACH verification. Card payments are charged automatically and may be retried after a failure; bank accounts must pass verification. Check the payment form for eligible card networks and account requirements.
Contract invoices can be paid by ACH or wire transfer, normally within 30 days of invoicing unless the order specifies otherwise. Prices exclude applicable taxes; customers are responsible for VAT, sales and other taxes and for supplying valid exemption documents. Users must be at least 18, have contractual capacity, and comply with applicable export and sanctions restrictions.
The order governs the subscription and cancellation terms. Standard terms renew orders for the original subscription period and generally require cancellation at least 60 days before its end; confirm the effective date of a self-service plan change in billing settings. Fees are generally non-refundable, subject to express contractual exceptions such as an uncured material breach. Export required data before termination, which can lead to permanent deletion.