api.video Pricing, Video API Transcoding Docs 2026

Why evaluate api.video pricing and video API transcoding docs in 2026?

api.video is a full-stack video API that handles upload, transcoding, hosting, delivery, player, and analytics through one platform. If you are searching for api.video pricing and video API transcoding docs in 2026, you are likely deciding between a complete video platform and a simpler hosted FFmpeg API for your encoding pipeline.

api.video positions itself as "video infrastructure for product builders." The platform offers free encoding (announced September 2023), pay-as-you-go storage and delivery, and claims 99.999% uptime across 140+ PoPs. It is trusted by JO Paris 2024, Continental, and Mercedes AMG Petronas.

Very Good FFmpeg takes a different approach. It runs your exact FFmpeg commands on dedicated 16-core CPU or Nvidia GPU machines and bills per GB processed. No storage fees, no delivery fees, no platform abstractions.

This article reviews api.video pricing in 2026, its transcoding documentation, developer sentiment across forums and review sites, and how the platform compares with hosted FFmpeg alternatives. It includes a step-by-step migration guide and concrete cost examples.

Key takeaways: What should you know about api.video in 2026?

api.video offers free encoding with paid storage and delivery. Very Good FFmpeg charges only for compute with no storage or delivery fees. The right choice depends on whether you need the full video platform or just raw transcoding power.

api.video free encoding is a strong differentiator. The platform uses custom ASIC hardware for encoding and covers input and output renditions at no cost. You pay only for storage and delivery of videos you keep and serve.

What is api.video?

api.video is a video API platform founded in 2018 and headquartered in Bordeaux, France. It provides a complete video stack through a single REST API: upload, transcoding, storage, CDN delivery, a customizable video player, and built-in analytics. The platform is EU-based, which matters for developers subject to GDPR requirements.

The company claims 99.999% uptime and operates 140+ points of presence for content delivery. api.video targets product builders who want to add video features to their applications without managing video infrastructure. SDKs are available for PHP, Android, Go, C#, Swift, Node.js, Python, and Java.

Key capabilities include:

• Video upload via direct upload, URL import, or multipart upload for large files.
• Automatic transcoding to multiple formats including HLS, MP4, and thumbnail generation.
• Customizable player with built-in analytics and engagement tracking.
• Live streaming with real-time transcoding.
• AI add-ons: transcription ($0.10/min), summarization ($0.05/min), translation.

api.video uses REST with an OpenAPI specification. Full documentation is at docs.api.video with interactive demos, SDK examples, and integration guides.

Very Good FFmpeg is simpler by design. It exposes a single POST endpoint. You pass the same FFmpeg flags, filter graphs, and codec options you would use in your terminal. No platform abstractions, no quality presets, no bundled storage. It is designed for developers who already know FFmpeg and want to run it in the cloud without managing servers.

# api.video: upload a video via URL import
curl -X POST https://ws.api.video/videos \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "My Video",
    "source": "https://example.com/input.mp4"
  }'

# Very Good FFmpeg: encode with raw FFmpeg command
curl -X POST https://verygoodffmpeg.com/api/ffmpeg \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "input_files": {
      "input.mp4": "https://your-bucket.s3.amazonaws.com/input.mp4"
    },
    "output_files": ["output.mp4"],
    "ffmpeg_commands": ["-i {{input.mp4}} -c:v libx264 -crf 23 -preset medium -c:a aac -b:a 128k {{output.mp4}}"]
  }'

The api.video API abstracts encoding. You specify quality tiers and configuration presets. Very Good FFmpeg passes your command directly to FFmpeg. If it works on your machine, it works through the API.

What does "transcoding docs" mean in the api.video context?

api.video transcoding docs refer to the documentation for how the platform handles video encoding. Unlike a hosted FFmpeg API where you specify exact FFmpeg commands, api.video abstracts encoding into quality tiers and configuration presets.

The api.video VOD documentation at docs.api.video/vod explains that uploaded videos are automatically transcoded to multiple formats. The platform handles resolution adaptation, bitrate selection, and format optimization based on your configuration.

Key transcoding details from the docs:

• Maximum input file size: 30 GiB per video.
• Maximum duration: 1440 minutes (24 hours) per video.
• Supported input formats: MP4, MOV, AVI, MKV, WEBM, and others.
• Output formats: HLS for adaptive streaming, MP4 for download, and thumbnail images.
• Encoding powered by ASIC hardware encoders.

The sandbox environment limits videos to 30 seconds, applies an unremovable watermark, and auto-deletes after 24 hours. Production rate limits are 100 upload calls, 200 write calls, and 500 read calls per minute. You cannot test real workloads without upgrading to a paid plan.

Very Good FFmpeg docs describe a single POST endpoint where you pass raw FFmpeg commands. There is no abstraction layer. Every FFmpeg flag, filter, and codec works because the API passes your command directly to FFmpeg on a dedicated instance.

How does api.video pricing work in 2026?

api.video pricing in 2026 has three main components: encoding (free), storage (per minute per month), and delivery (per minute served).

api.video made encoding free in September 2023. The company announced that custom ASIC hardware encoding was fast enough and cheap enough to absorb the cost. This was a significant move that positioned api.video ahead of competitors who still charge per-minute encoding fees.

Storage at $0.00285 per minute per month means 1,000 minutes of stored video costs $2.85 per month. Delivery at $0.0017 per minute means streaming 1,000 minutes costs $1.70.

A Hacker News pricing comparison from a video infrastructure engineer (Sep 2020) puts api.video in the middle of the market for live streaming input: api.video at $2.40 per input hour, AWS IVS at $2.00, and Mux at $4.20. These numbers are dated but still useful for relative positioning.

Enterprise plans include SAML SSO, isolated storage, SLAs, and higher rate limits (200 upload, 1,000 write, 2,500 read calls per minute). There is no published pricing for enterprise tiers. You must contact sales.

What is free versus paid on api.video?

Understanding what costs money versus what is free is important for estimating your monthly bill.

The free encoding policy covers both input and output renditions. If you upload a 10-minute video and api.video generates 5 output renditions, encoding costs zero. You pay only for storage of those renditions and delivery when viewers watch them.

This model is different from competitors who charge per-minute encoding fees for each rendition. api.video makes money on storage and delivery rather than on the encode itself. Mux has argued this model can hide cross-subsidization where some customers overpay while others get unsustainable deals.

How do the docs compare between api.video and a hosted FFmpeg API?

api.video docs are comprehensive for a full video platform. The documentation covers uploading, transcoding, delivery, player integration, analytics, and live streaming. Interactive API demos let you test endpoints directly in the browser.

Very Good FFmpeg docs are focused on the single encoding endpoint. They cover the REST API reference, limits, hardware specs, and SDK integrations. The product surface is smaller, so the docs are shorter and targeted at developers who already understand FFmpeg.

api.video docs are better for teams adopting a full video platform. Very Good FFmpeg docs are better for developers who already have FFmpeg commands and need a REST wrapper.

How does the pricing compare for a real workload?

Here is a concrete cost comparison for a typical encoding workload.

A developer needs to transcode 500 videos per month. Each video is 5 minutes long, HD resolution. The output needs to be delivered to viewers.

On api.video, encoding is free. Storage for 500 videos at 5 minutes each is 2,500 minutes. At $0.00285/min/month, storage costs $7.13/mo. If each video is viewed 10 times, delivery is 25,000 minutes at $0.0017/min for a cost of $42.50/mo. Total estimated: $49.63/mo.

On Very Good FFmpeg, 500 videos at roughly 200 MB output each is 100 GB of processed usage. The first 2 GB is free. The next 8 GB at $0.50/GB is $4.00. The remaining 90 GB at $0.10/GB is $9.00. Total estimated: $13.00/mo. Storage and delivery are billed separately by your own provider (S3, CloudFront, Cloudflare R2, etc.).

api.video total is higher but includes player, analytics, CDN, and platform features. Very Good FFmpeg total is lower but you handle storage and delivery yourself.

Who should use api.video?

api.video is a strong choice when you need a complete video product without building infrastructure from scratch.

Use api.video when:

1. You are building a product that needs upload, transcoding, hosting, delivery, and analytics from one vendor.
2. You want free encoding to keep costs low during growth.
3. Your team prefers a structured API with platform conventions over raw FFmpeg commands.
4. You need a customizable video player with built-in engagement tracking.
5. You serve video to end users and need CDN delivery across multiple regions.
6. You are based in the EU or have GDPR compliance requirements and want an EU-hosted video provider.

api.video is well-suited for SaaS products, marketplaces, e-learning platforms, and any application where video is a core feature but video infrastructure is not your team's focus.

Who should skip api.video and use a hosted FFmpeg API instead?

A hosted FFmpeg API like Very Good FFmpeg is better when you only need encoding without the platform layer.

Skip api.video when:

1. You already have storage and CDN infrastructure and do not want to pay for bundled storage and delivery.
2. You need full control over FFmpeg codec flags, filter graphs, and encoding parameters.
3. You process batch transcoding workloads where output goes to your own S3 bucket or archive.
4. You want flat per-GB compute pricing without tracking storage-minutes and delivery-minutes.
5. Your team already knows FFmpeg and wants to use the same syntax on the API.
6. You do not need a video player, analytics, or streaming features.

Very Good FFmpeg charges per GB processed. There are no storage fees, delivery fees, or platform abstractions. The API accepts the same FFmpeg commands you run locally.

Does api.video support every FFmpeg codec and filter?

No. api.video encodes videos to supported output formats and resolutions through quality configurations. You do not pass raw FFmpeg flags to the api.video API.

Supported output formats include HLS for adaptive streaming, MP4 for progressive download, and thumbnail images. The platform handles codec selection, resolution scaling, and bitrate optimization.

Very Good FFmpeg supports every codec and filter that a standard FFmpeg build supports: H.264, H.265/HEVC, AV1, VP9, ProRes, AAC, Opus, and the full filter graph. If it works in your terminal, it works through the API.

If your pipeline depends on specific FFmpeg features like custom filter graphs, audio mixing, or subtitle burning, a hosted FFmpeg API is the more direct option.

Can you use api.video just for transcoding?

Technically yes, but it is not cost-effective compared to a hosted FFmpeg API. api.video is designed as a full video platform. If you transcode a video through api.video and download the output instead of streaming it, you still pay storage costs for the encoded files.

api.video pricing assumes the output will be stored and streamed through their platform. The free encoding is a feature that makes the storage and delivery model more attractive, not a standalone transcoding service.

For pure transcoding where you control your own storage, Very Good FFmpeg is cheaper and more direct. You pay only for compute time. Output files are returned as download URLs, then you can copy them into your own S3 bucket or archive.

# Very Good FFmpeg: transcode and get an output URL
curl -X POST https://verygoodffmpeg.com/api/ffmpeg \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "input_files": {
      "input.mp4": "https://your-bucket.s3.amazonaws.com/input.mp4"
    },
    "output_files": ["output.mp4"],
    "ffmpeg_commands": ["-i {{input.mp4}} -c:v libx264 -crf 23 -c:a aac -movflags +faststart {{output.mp4}}"]
  }'

No lingering storage costs. No delivery fees. The encoded file is available from the job result, and you can move it into your own storage.

What do developers say about api.video?

Developer sentiment on api.video is generally positive, particularly around the free encoding announcement and the quality of documentation. There are also critical perspectives worth considering.

On Hacker News, a video infrastructure engineer compared live input pricing across platforms (Sep 2020). api.video at $2.40 per input hour was mid-range: cheaper than Mux ($4.20) but more expensive than AWS IVS ($2.00). The same thread noted that platforms use just-in-time encoding to limit costs for low-viewership streams.

A separate HN thread (Feb 2022) highlighted api.video as one of the few EU-based video API platforms with GDPR compliance. For European developers subject to GDPR, this is a meaningful advantage over US-based alternatives like Mux or Cloudinary.

On SaaSHub, api.video is the top-ranked Mux alternative with 10 community votes. It is listed alongside alternatives where Mux ranks first overall, followed by Bunny.net and Brightcove. On AlternativeTo, users compare api.video with CloudFront, Bunny.net, and Livepeer.

Product Hunt engagement for api.video is notably low: 14 followers, 3 launches, and zero user reviews. Mux has 5 reviews with a 5.0 rating. The lack of grassroots developer advocacy is worth noting.

Mux published a blog post in April 2026 arguing that "simple" infrastructure pricing is often deceptive: "if it feels too cheap to be true, someone or something is subsidizing your use case." This challenges api.video's "free encoding" model. Mux cut list pricing by 17-23% in July 2025 and now offers 100,000 free delivery minutes per month across all resolutions, narrowing the gap with api.video.

The api.video compare page targets AWS, Azure, Bitmovin, Kaltura, and Brightcove. Notably absent from that comparison page are Mux (the closest competitor on developer experience), Cloudinary, and hosted FFmpeg APIs. This suggests api.video positions against legacy enterprise vendors rather than modern developer-focused alternatives.

What are the hidden costs of api.video?

api.video pricing is transparent for the core services, but there are costs to understand.

1. Storage costs accumulate monthly. Every minute of video stored incurs the $0.00285/min fee each month. If you store 10,000 minutes, that is $28.50 every month.
2. Delivery costs apply per minute streamed. Popular videos with many views mean delivery costs scale linearly with audience size.
3. The sandbox 30-second limit means you cannot fully test longer videos without upgrading.
4. Enterprise features like white-label player and live streaming require custom pricing.
5. AI features (transcription, summarization, translation) are not included in the base pricing.

Very Good FFmpeg has fewer cost categories. Only processed GB is billed. Output URLs and webhook delivery are included. Failed or cancelled jobs are billed for the bytes processed before they stop. No monthly minimum for most accounts.

How do you migrate from api.video to a hosted FFmpeg API?

If you decide api.video is more platform than you need, here is how to migrate to Very Good FFmpeg.

1. Export your videos from api.video. Download source files or encoded outputs via the API.

curl -X GET https://ws.api.video/videos/$VIDEO_ID/source \
  -H "Authorization: Bearer $API_KEY" \
  -o video.mp4

2. Identify the equivalent FFmpeg command. api.video abstracts encoding into quality presets. A typical HD preset maps to -c:v libx264 -crf 23 -preset medium -c:a aac -b:a 128k. Check your output specs to confirm.

3. Rewrite as a raw FFmpeg command. Replace the platform preset with direct flags.

-i input.mp4 -c:v libx264 -crf 23 -preset medium -vf scale=1920:1080 -c:a aac -b:a 128k -movflags +faststart output.mp4

4. Test locally. Run the command on the exported file to verify output matches.

ffmpeg -i video.mp4 -c:v libx264 -crf 23 -preset medium -vf scale=1920:1080 -c:a aac -b:a 128k -movflags +faststart output.mp4

5. POST to the hosted FFmpeg API.

curl -X POST https://verygoodffmpeg.com/api/ffmpeg \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "input_files": {
      "input.mp4": "https://your-bucket.s3.amazonaws.com/video.mp4"
    },
    "output_files": ["output.mp4"],
    "ffmpeg_commands": ["-i {{input.mp4}} -c:v libx264 -crf 23 -preset medium -vf scale=1920:1080 -c:a aac -b:a 128k -movflags +faststart {{output.mp4}}"],
    "webhook_url": "https://your-app.com/webhook"
  }'

6. Move output to your own storage. Read the output URL from the completed job or webhook payload, then copy the file to S3, Cloudflare R2, or your archive. You control the data from this point forward.

Verdict: Which should you choose?

There is no single right answer. The choice depends on your workload and infrastructure.

api.video is the right choice when:

• You need a complete video product (upload, transcode, host, deliver, player, analytics) from one vendor.
• Free encoding is a significant cost advantage for your use case.
• Your team prefers platform conventions over raw FFmpeg.
• You need EU-based hosting for GDPR compliance.

Very Good FFmpeg is the right choice when:

• You only need encoding and already have storage and delivery infrastructure.
• You need full FFmpeg control (filter graphs, custom codecs, pixel formats).
• You want simple per-GB pricing without tracking storage-minutes and delivery-minutes.
• You process batch transcoding where output goes to your own storage.

api.video total cost is higher but includes more services. Very Good FFmpeg total cost is lower but you bring your own storage and CDN. If you only need hosted FFmpeg, Very Good FFmpeg is cheaper and more flexible. If you need an end-to-end video product, api.video is a solid choice.

FAQ

Does api.video have a free tier?

api.video offers a sandbox environment that is free to use. The sandbox limits videos to 30 seconds, applies a watermark, and auto-deletes after 24 hours. There is no free tier for production storage or delivery.

Does Very Good FFmpeg have a free tier?

Yes. Very Good FFmpeg includes 2 GB of free processed usage per month. No credit card is required to start. There is no monthly subscription fee.

Does api.video support live streaming?

Yes. api.video offers live streaming with real-time transcoding. Live streaming requires a paid plan and custom configuration. HN pricing data (2020) shows api.video at $2.40 per input hour for live.

Does Very Good FFmpeg support live streaming?

No. Very Good FFmpeg is designed for on-demand encoding jobs. For live streaming, use a dedicated live platform.

Can I use api.video for just file transcoding without their player or analytics?

You can encode files through api.video without using their player or analytics. However, you still incur storage costs for the encoded output. For transcoding where the output goes to your own storage, a hosted FFmpeg API is more cost-effective.

Is api.video GDPR compliant?

Yes. api.video is based in Bordeaux, France, and is EU-based. This was noted in HN discussions as one of the few EU-based video API options available. This is important for European developers subject to GDPR data sovereignty requirements.

Which is cheaper for 500 videos per month?

api.video costs approximately $49.63/mo including storage and delivery. Very Good FFmpeg costs approximately $13.00/mo for compute only. You handle storage and delivery separately with Very Good FFmpeg. Combined with S3 and CloudFront, total cost is still typically lower than api.video.

Does api.video charge for encoding at 4K?

No. api.video made encoding free at all qualities including 4K in September 2023. The free encoding policy covers both input and all output renditions.

How does Mux pricing compare in 2026?

Mux reduced list pricing by 17-23% in July 2025 and now offers 100,000 free delivery minutes per month across all resolutions including 4K. Mux still charges per-minute encoding fees (unlike api.video) but has narrowed the gap with free delivery minutes and free basic encoding (since October 2023).

References

Pricing, documentation, and feature data captured June 2026. Verify before making a decision.

1. api.video pricing: https://api.video/pricing
2. api.video main site: https://api.video
3. api.video API reference: https://docs.api.video/reference
4. api.video VOD docs: https://docs.api.video/vod
5. api.video free encoding announcement: https://api.video/blog/product-updates/video-encoding-pricing-update/
6. api.video vs AWS: https://api.video/compare/amazon-web-services
7. api.video vs Bitmovin: https://api.video/compare/bitmovin
8. api.video compare page: https://api.video/compare
9. SaaSHub alternatives: https://www.saashub.com/api-video-alternatives
10. AlternativeTo: https://alternativeto.net/software/api-video/
11. Hacker News pricing comparison (Sep 2020): https://news.ycombinator.com/item?id=24552462
12. Hacker News GDPR mention (Feb 2022): https://news.ycombinator.com/item?id=30160413
13. Mux pricing philosophy (Apr 2026): https://www.mux.com/blog/simple-infra-pricing-doesn-t-work
14. Mux price drop (Jul 2025): https://www.mux.com/blog/price-drop
15. Mux CEO on pricing (Jul 2025): https://www.mux.com/blog/in-this-economy
16. Product Hunt api.video: https://www.producthunt.com/products/api-video
17. Very Good FFmpeg: https://verygoodffmpeg.com