Questions
Where your file goes, what runs where, and what costs money.
Questions
What happens to my file?
On a browser-lane operation, nothing: it is read by the page, worked on in memory, and handed back as a download. No request carries it. On a server-lane operation it is sent to our API, processed, and not retained unless you save it to a project.
Do I need an account?
Not to do the work. An account is asked for when you want to save a project, run more than three server operations in a day, batch, or use an API key.
How big a file can I edit?
In the browser, as big as your machine can hold — there is no server limit to hit because there is no server. The 25 MB cap is on the server lane only.
Why does converting an image re-encode it?
Because a canvas operation decodes and re-encodes: it costs you the original resolution metadata and bakes one quality decision in. That is the honest price of not uploading, it is stated on every page it applies to, and the server lane is there for when you would rather pay the other price.
Can I run these from a script?
The server-lane operations are adapter functions, so they are already HTTP endpoints and MCP tools. The browser-lane ones are not — they only exist in a page, which is the point of them.