Pixazo API→Video Compressor API

Video Compressor API

Compress video to a target file size or bitrate while keeping the quality you choose, through the Video Compressor API. This online video compressor speeds up delivery, cuts storage and bandwidth costs, and clears upload-size limits automatically inside your pipeline — instead of running desktop tools or one-off scripts to compress video on every file.

Explore Models

Explore Video Compressor API Models

We’re adding models to the Video Compressor API. Here’s how it will let you compress video and trade file size against visual quality once it goes live.

Browse by Capabilities

Coming soon

Video Compressor API models are on the way

Compress any video to a target size or bitrate while preserving quality, via API. We're adding models to this category — check back soon.

Browse available models →
In active development · Coming soon

Compress video to any size — without wrecking quality

The Video Compressor API will compress a video to a target size or bitrate while preserving as much visual quality as you choose — so delivery is faster, storage and bandwidth are cheaper, and files fit under upload limits.

It is an online video compressor built for pipelines: compress every user upload before it hits storage, generate lightweight preview renditions, or normalize a media library to a consistent size profile — all through one call per file rather than manual tools.

What savings can you expect?

Illustrative planned targets (not a guarantee) for a 1-minute 1080p clip:

Quality tierApprox. size afterCodecBest for
Visually lossless~60–70% of originalH.265 / AV1Delivery where quality matters
Balanced~35–45% of originalH.264 / H.265Web & app playback
Aggressive~15–25% of originalH.264Previews, thumbnails, drafts
Why compress via API?

Automate compression in your upload pipeline instead of running desktop tools — one call per file, consistent output, predictable cost, and no manual work as volume grows.

How you’ll control it

Set a target size (e.g. “under 10 MB”) or a target bitrate, choose a codec and quality tier, optionally downscale resolution — and the API handles the encode.

Planned input support
  • MP4, MOV, WebM, MKV and AVI sources
  • Target-size and target-bitrate modes
  • Codec selection (H.264 / H.265 / AV1) or automatic
  • Optional resolution downscale (e.g. 4K → 1080p)
When not to compress: If you need a bit-exact archival master or you’re re-compressing an already-heavily-compressed file, another pass can hurt quality for little gain. Compression is lossy — keep an untouched original where fidelity is critical.

Common questions

How much will the Video Compressor API reduce file size?
Typical target reductions are 40–80% depending on the source and the quality tier you pick. Exact ratios depend on the original codec, resolution and bitrate, and will be published with the endpoint — nothing is claimed as guaranteed until launch.
Will quality drop when I compress video?
You choose the trade-off. A "visually lossless" tier keeps quality high with modest savings; a "balanced" tier suits web and app playback; an "aggressive" tier maximizes savings for previews and thumbnails.
What codecs are planned?
H.264 for maximum compatibility, and H.265 (HEVC) / AV1 for higher efficiency at the same quality. You will be able to pick a codec or let the video compressor choose based on your target.
Can I compress a video to a specific file size?
Yes — a target-size mode ("keep it under 10 MB") and a target-bitrate mode are both planned, alongside an optional resolution downscale.
Will it change the resolution or aspect ratio?
Only if you ask it to. An optional downscale (e.g. 4K → 1080p) is available for extra savings, but by default the resolution and aspect ratio are preserved.
Is it lossless?
No — video compression at these ratios is lossy by design. The "visually lossless" tier minimizes perceptible loss, but if you need a bit-exact copy, compression is not the right tool.