How to encode prores online — no mac required
- Step 1Open the encoder in a Chromium browser — Use Chrome or Edge on Windows, Linux, or ChromeOS. The tool is a Pro-media feature (
minTier: pro_media) — confirm your plan, since ProRes output is large regardless of platform. - Step 2Drop your source video — Drag in any MP4, MOV, MKV, WebM, AVI, M4V, or TS. One file per run. It is read into the browser locally — nothing uploads, the same on every OS.
- Step 3Pick the profile you need — The only control is Profile:
422for editorial,422hqfor a client/broadcast master,4444for alpha. All three encode identically on Windows, Linux, and ChromeOS — the OS does not change the output. - Step 4Choose where to save the MOV — The tool streams output, so your browser prompts for a save location (a
…-prores.movname is suggested). On browsers without the File System Access API the file downloads when done — common on Linux Firefox, so prefer Chrome/Edge for the streaming save. - Step 5Run the encode locally — FFmpeg.wasm runs
prores_kson your CPU. Encode speed depends on your machine, not a server — a fast PC keeps pace with a Mac running native FFmpeg for the same job. - Step 6Hand the MOV to any editor on any OS — The
.movimports as native ProRes in Final Cut (Mac), Premiere and Resolve (Mac/Windows/Linux). Send it to a Mac-based editor and it just works — no transcode on their end.
Platform support for browser ProRes encoding
The encode is identical across platforms — it is FFmpeg.wasm, not a native OS encoder. Browser support governs the streaming save.
| Platform | Browser | Encodes ProRes? | Streaming save to disk? |
|---|---|---|---|
| Windows | Chrome / Edge | Yes | Yes (File System Access API) |
| Linux | Chrome / Edge | Yes | Yes |
| Linux | Firefox | Yes | No — downloads at end |
| ChromeOS (Chromebook) | Chrome | Yes | Yes |
| macOS | Chrome / Edge / Safari | Yes | Chrome/Edge yes; Safari downloads |
Profiles available on every OS
Same three profiles everywhere — the OS never changes the encode. There is no Proxy/LT option.
| Profile value | `-profile:v` | Pixel format | Use |
|---|---|---|---|
422 | 2 | yuv422p10le | Editing |
422hq | 3 | yuv422p10le | Master/finishing |
4444 | 4 | yuva444p10le | Alpha/VFX |
Tier limits (same on all platforms)
ProRes encoding requires Pro-media regardless of OS. Limits are by file size and batch count.
| Tier | Max file size | Files / batch | ProRes access |
|---|---|---|---|
| Free | 1 GB | 1 | No |
| Pro | 10 GB | 5 | No |
| Pro-media | 100 GB | 50 | Yes |
| Developer | 100 GB | Unlimited | Yes |
Cookbook
Real cross-platform encodes for PC and Linux editors. The commands are the FFmpeg.wasm equivalents the profile picker drives — identical output on every OS.
Windows editor delivering ProRes to a Mac finishing house
A Premiere-on-Windows editor needs to hand a ProRes 422 HQ master to a Mac-based finishing house. Encode it in the browser; the Mac reads it natively.
OS: Windows 11, Chrome
Input: cut.mp4 (H.264, 1080p)
Profile: 422hq
In-browser equivalent:
prores_ks -profile:v 3 -pix_fmt yuv422p10le \
-vendor apl0 -c:a pcm_s16le
Output: cut-prores.mov → opens as ProRes 422 HQ on macOS.Linux editor with no native ProRes encoder
Resolve on Linux can't export ProRes (Apple's encoder isn't licensed there). The browser fills the gap with FFmpeg.wasm.
OS: Ubuntu, Chrome Input: timeline-export.mov (DNxHR or H.264) Profile: 422 Output: timeline-export-prores.mov (ProRes 422) → a ProRes file produced on Linux without any native Apple codec.
Chromebook student making ProRes for a class project
A Chromebook has no pro video apps, but the browser encoder runs fine on ChromeOS.
OS: ChromeOS, Chrome Input: project.webm Profile: 422 Output: project-prores.mov (ProRes 422) → hand it to a classmate's Final Cut Mac; imports natively.
Same source, identical output on Windows and macOS
Because it is FFmpeg.wasm, the encode is deterministic across OSes — the bytes are the same whether you ran it on a PC or a Mac.
Windows Chrome: source.mp4 → Profile 422 → source-prores.mov macOS Chrome: source.mp4 → Profile 422 → source-prores.mov Same prores_ks args, same yuv422p10le, same vendor apl0. The OS does not change the result.
Firefox-on-Linux falls back to download
On a browser without the File System Access API the result downloads instead of streaming to a chosen folder — still a valid ProRes file.
OS: Linux, Firefox Input: clip.mkv Profile: 422 No save-location prompt → clip-prores.mov downloads to ~/Downloads (For a streaming save to a chosen folder, use Chrome or Edge.)
Edge cases and what actually happens
Output is genuine ProRes a Mac accepts
SupportedEven though no Apple software is involved, the file is true ProRes: prores_ks with the correct -profile:v and pixel format plus the Apple vendor tag apl0 in a QuickTime MOV. A Final Cut editor on macOS imports it as a native ProRes asset — the OS that created it is irrelevant.
Firefox has no streaming save
Falls back to downloadThe File System Access API that streams output to a chosen folder is not in Firefox. The encode still runs and a valid ProRes MOV downloads at the end. For the streaming save (and best big-file behaviour) use Chrome or Edge.
Encode speed depends on the local CPU
ExpectedThere is no server doing the work — FFmpeg.wasm runs on your machine, so a faster CPU encodes faster, and an older laptop is slower. This is the same trade on every OS: local compute and zero upload instead of a cloud queue.
Not available on Free or basic Pro
403 tier-gatedProRes encoding requires the Pro-media tier (minTier: pro_media) on every platform — the OS does not change the gating. Pro-media also raises the per-file video limit to 100 GB.
Output is much larger than the source
By designProRes is intra-frame, so output runs 5–20× the H.264/H.265 source on any OS. PC and Linux editors should plan disk space accordingly; trim with the lossless trimmer first to encode only what you need.
Trying to encode on a mobile browser
Use desktopProRes encoding is heavy and the streaming-save API and memory headroom are best on desktop Chromium browsers. Use Chrome/Edge on Windows, Linux, ChromeOS, or macOS rather than a phone.
File over the tier size limit
413 too largeSources above your tier's video cap (Pro-media/Developer 100 GB) are rejected before encoding on any platform. Split a very long source with the video splitter and encode the pieces.
Wanted hardware-accelerated speed
Software encodeProRes here runs as a software encode in FFmpeg.wasm — there is no WebCodecs hardware ProRes encoder in browsers. Other tools like the H.265 encoder and AV1 encoder can use a hardware path; ProRes does not, so plan for CPU-bound timing.
Image-only or audio-only file dropped in
Invalid inputThe encoder needs a video container with a video stream, on every OS. A still image or an audio file fails. Provide a video source.
Frequently asked questions
Can I really make Apple ProRes without a Mac?
Yes. The tool runs FFmpeg's prores_ks encoder compiled to WebAssembly, so it encodes genuine ProRes in Chrome or Edge on Windows, Linux, or a Chromebook. The file uses the correct ProRes profile, pixel format, and the Apple vendor tag apl0, so Macs read it as native ProRes.
Will a Final Cut editor on a Mac accept my PC-made file?
Yes. The output is a standard QuickTime ProRes MOV — Final Cut, Premiere, and Resolve on macOS import it as native ProRes with no transcode. The OS that created it makes no difference to the bytes.
Does my footage upload to a server?
No. The entire encode runs locally in WebAssembly on your CPU. Nothing is uploaded on any platform — there is no cloud queue and no bandwidth limit, just local compute.
Which browsers work best?
Chromium browsers — Chrome and Edge — give you the streaming save to a folder you choose via the File System Access API. Firefox encodes fine but downloads the result instead. Use a desktop browser, not mobile, because ProRes encoding is memory-heavy.
Is the output identical across operating systems?
Yes. It is FFmpeg.wasm, so the same source and profile produce the same ProRes bytes whether you ran it on Windows, Linux, ChromeOS, or macOS. The prores_ks arguments and pixel format do not change with the OS.
Which profiles can I use on a PC?
All three, identically to a Mac: 422 for editing, 422hq for a master, and 4444 for alpha/VFX. Pick from the single profile control. There is no Proxy or LT option.
Why is encoding slow on my laptop?
The work is done by your CPU via WebAssembly, not a server, so an older or low-power machine takes longer. The upside is no upload and complete privacy. A modern multi-core PC keeps reasonable pace for a software ProRes encode.
Is ProRes hardware-accelerated here?
No. ProRes runs as a software encode — browsers have no hardware ProRes encoder via WebCodecs. If you want a hardware-accelerated path for delivery codecs, the H.265 encoder and AV1 encoder can use one; ProRes stays CPU-bound.
Do I need to install FFmpeg?
No. FFmpeg is bundled as WebAssembly and loads in the browser — there is no system FFmpeg install, no PATH setup, and no command line. You only pick a profile and run.
How big can my source be on a PC?
Up to your tier's video limit — Pro-media and Developer allow 100 GB per file, the same on every OS. Output streams to disk, so there is no duration cap, only file size and batch count.
Can I encode on a phone or tablet?
It is not recommended. ProRes encoding is memory- and CPU-heavy, and the streaming-save API works best on desktop Chromium. Use Chrome or Edge on a desktop or laptop for reliable results.
What tier do I need?
Pro-media or higher (minTier: pro_media), the same across all platforms. Free and basic Pro cannot run the ProRes encoder. Pro-media also unlocks the 100 GB per-file video limit ProRes output typically needs.
Privacy first
Every JAD Video tool runs entirely in your browser via WebCodecs and FFmpeg (WebAssembly). Your video files never leave your device — verified by zero outbound network requests during processing.