Support
Help centre
The questions this site actually raises — where your files go, why some tools need a server, and what a plan changes. If the answer is not here, the routes at the bottom of the page reach a person.
11 of 11 articles
Do my files get uploaded?Privacy & files
For 321 of the 629 tools, no. They run as WebAssembly inside your own browser tab — the file is read from disk by the page, processed on your machine, and the result is handed straight back. Nothing leaves the device, so there is nothing for us to store, log or delete.
The remaining 308 need a server: they depend on tooling too large to ship to a browser, or on work that would take minutes on a laptop. Those upload the file, process it on our own infrastructure, and hand back a download.
Every tool page states which of the two it is before you choose a file, and the badge is resolved server-side so it is correct on first paint — not something that changes once the page finishes loading.
How long do you keep an uploaded file?Privacy & files
A server job holds its input and output in object storage so you can download the result. Both are deleted an hour after upload if you are not signed in, and 24 hours if you are — whether or not you came back for them. Signing in is what extends it; the plan you are on makes no difference.
Files handled in your browser are never uploaded at all, so there is no retention question for those.
For the exact commitments, including how to make a deletion request, read the privacy notice.
Do I need an account?Accounts
Not to use a tool. Every tool on the site opens and runs without signing in, and that is not a trial — it is how the free tier works.
An account exists for the things that need one to be possible at all: server jobs tied to your quota, API keys, saved workflows, team members and billing.
What are the file size and usage limits?Plans & billing
Free covers 10 server-processed files a day, up to 25 MB each. Pro raises the ceiling to 1 GB per file with no daily cap, and Business to 5 GB.
Those caps apply to work our servers do. A tool running in your browser is bounded by your own machine and your browser’s memory, not by a plan.
API access is separate: Pro includes 1,000 calls a month and Business 10,000.
How do I cancel or change my plan?Plans & billing
Billing lives in your dashboard, under Billing. A change takes effect on the current cycle and the plan drops to free at the end of the paid period — nothing is deleted when it does.
If a charge looks wrong, send the invoice reference through contact with the billing topic; that reaches the people who can actually refund it.
How do I run a tool from my own code?API
Create an API key in the dashboard, then call the jobs endpoint with a tool slug and your input files. Keys are Bearer tokens beginning ax_live_.
Anonymous traffic is limited to 60 requests a minute per IP; an API key raises that to 600 per key. Every response carries x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset so a client can pace itself without guessing.
The full reference, including request and response shapes for every endpoint, is generated from the same schema the server validates against.
I lost my API key — can you send it again?API
No, and that is deliberate. The full key is shown once, at the moment it is created, and only a hash is stored afterwards. The dashboard can show you the last four characters to identify a key, never the key itself.
Revoke the old key and create a new one. A revoked key stops working immediately.
A tool failed or gave the wrong resultTroubleshooting
Check status first — if the API or the workers are degraded, that accounts for most sudden failures and it will clear without you doing anything.
If status is clean, it is worth reporting. The two things that make a bug fixable are what you did and what happened instead; the file type and rough size usually matter too.
A tool will not start in my browserTroubleshooting
In-browser tools need WebAssembly and, for the larger ones, enough memory to hold the file plus its working copy. A very large file on a low-memory device is the usual cause of a tab that stalls or reloads itself.
Private or hardened browsing modes that block WebAssembly will stop these tools from starting at all. The same tool run as a server job is unaffected.
The tool I need does not existTools
Search first — there are 629 tools and the naming is not always what you would guess, so the job you want is often filed under a different name.
If it genuinely is not there, describe the job rather than the tool name. Requests are grouped by the task they describe, and the tasks several people ask for get built.
I found a security vulnerabilityPrivacy & files
Please report it through the security disclosure route rather than the public bug form, so it is not sitting in an ordinary queue while it is still exploitable.
Do not include working exploit payloads against live accounts; a description of the flaw and how to reproduce it is enough to act on.
Still stuck?
Pick the route that matches the problem — each one goes to the people who can act on it, which is faster than a single inbox that has to be sorted first.