Pricing

Credits pay for cloud rendering: renders started from the cloud, a template form or the API. One credit is 5 seconds of render time, so Premium’s 150 credits cover about 12.5 minutes of rendering a month.

Renders are charged for the time they actually take, to the hundredth of a credit, so a 12-second render costs 2.4 credits rather than 3. How long a render takes depends on its length, resolution and effects. Every render and its cost is listed in your dashboard.

No. Exporting from the editor renders on your own machine and is free and unlimited on every plan. Credits are only used by renders that run on our servers.

Cloud renders pause until your allowance resets at the start of your next billing month, or until you add the extra credits add-on. We never bill you for going over, and unused credits do not roll over.

Each person who signs in to your account needs a seat. Individual is a single seat. Premium includes one, and extra seats cost the same as the first, billed on the same cycle as your plan.

Yes. When you reach your included storage you can free up space, add the Extra storage add-on or upgrade. You are never charged for going over.

Yes, from your dashboard, at any time. If you cancel you keep your paid features until the end of the current billing period. Your account then moves to the Free plan, with your projects kept for a while so you can export them or resubscribe.

No. The editor opens straight in your browser with no sign-up and no card. Free projects live in your browser only, so export anything you want to keep, or move to a paid plan to save them in the cloud.

Chrome, Edge and Firefox on a desktop computer: Mac, Windows or Linux. Use a current version of any of them and you are fine.

The editor draws every frame on your graphics card and codes video inside the browser, so it needs a browser that supports those APIs and a machine with a working graphics card.

Your browser is drawing with the processor instead of the graphics card. Some machines have none to offer, but far more often the browser has hardware acceleration switched off in its settings, or a driver problem has disabled it.

We block this rather than let you carry on because software rendering is not simply slower. On several common drivers it produces wrong output: masks punch holes in the wrong place, effects come out corrupted, and the video you export does not match what you see.

In Chrome or Edge, go to Settings › System and turn on ‘Use graphics acceleration when available’. In Firefox, go to Settings › General › Performance, clear ‘Use recommended performance settings’ and turn on ‘Use hardware acceleration when available’. Restart the browser completely, then reload the editor.

No. The editor needs a graphics card, a mouse and a keyboard, so it runs on desktop computers only. There is no mobile version planned.

Filling in a template form is different. Forms work on a phone, they just leave out the live preview: your answers submit normally and the video renders on our servers, so you can send a form to someone who only has a phone.

The editor needs a window of at least 1000 by 600 pixels to fit its panels and timeline, and below that it covers itself rather than show you a layout you cannot work in. Nothing is lost: make the window bigger and you drop straight back into your project, still open where you left it.

Email us and say which message you saw. Detection is not perfect, and if we have turned away a machine that should work we want to know about it: we can let you through while we fix the check.

Everything in Premium, with the seats, cloud render credits and storage your team needs, a custom agreement with invoicing, and support commitments to match. Email us and we will put a plan together.

Plans are paid by card through Stripe and renew automatically until cancelled. Yearly billing works out two months cheaper than paying monthly. Prices are in US dollars and exclude VAT and sales tax where they apply.