The web app, API and CLI run on the same quota. A compression run is only counted when the output actually gets smaller — failures and no-gain results never are. A successful upscale costs 1 run — the output is by design larger than the input, so the “smaller output” rule does not apply to it. Failed upscales, timeouts and invalid input are never charged.
Free
¥0
Every shipped capability is free to use right now.
Use it directly: Web compressor · Command line · Developer docs
No. Failures never count, and neither do results that don't get smaller — the original is kept unless you convert, and an explicit conversion still returns the converted file even when it isn't smaller. Only output that actually shrinks counts as one run. Upscaling is the exception to that rule — see below.
A successful upscale costs 1 run — the output is by design larger than the input, so the “smaller output” rule does not apply to it. Failed upscales, timeouts and invalid input are never charged. Upscaling draws on the same quota as compression.
Daily for signed-out visitors, monthly for accounts. The reset time is shown in your dashboard.
Yes — one account, one pool. Web, API and CLI all draw on it.
A conversion costs 1 extra run on top of the compression: compress and convert to WebP counts as 2. Converting to the source format counts as 1, and failed conversions never count.