There is no hardware compatibility list to work through, because the studio runs in the browser. What matters is a current browser, hardware acceleration, enough memory for the timeline you open and a connection that can stream your media.
The studio is built for current Chromium browsers. Keep the browser updated, allow hardware acceleration and close heavy extension tabs before a long render session.
Media streams to the browser, so the connection sets the ceiling on how many tracks play cleanly. Proxies lower that ceiling dramatically for high resolution jobs.
The viewer uses the GPU through the browser. Any modern integrated or discrete GPU handles grading and editing; the timeline complexity, not the page, is what asks for memory.
Camera media lives where you keep it and streams into the project; the project itself, its versions and its renders live in the studio, so a lost laptop does not lose the edit.
The short version of what the browser studio expects.
System requirements questions that come up before a first render.
Current Chrome and Edge releases, plus the version before them. Safari and Firefox are not supported for editing yet, and older Chromium builds may miss features the viewer needs.
Yes for editing, colour and review work. Keep the number of simultaneous video tracks sensible and use proxies for high resolution media.
Around 15 Mbps is comfortable for 1080p work and 50 Mbps for 4K. Slower connections still work for trimming and grading if you generate proxies first.
No. Integrated graphics with hardware acceleration enabled run the viewer, scopes and mixer. A discrete GPU helps mainly with the largest 8K timelines in the browser.
For short sessions, yes. Use proxies, keep the timeline simple and download deliverables once you are back on a stable connection.
The studio is one project with several pages. These are the pages that usually come before and after this one.
Open the studio and load a clip. If the viewer plays and the scopes move, the machine is already good enough to edit on.
