4.5/5
G2 rating
1 verified review
Report
Should I Use Very Good FFmpeg?
Hosted FFmpeg API with usage-based pricing from $0.50/GB down to $0.08/GB. Run any FFmpeg command on dedicated 16 vCPU / 32 GB infrastructure with 99.99% uptime, async webhooks, and no $0 monthly minimum. First 2 GB free.
Depends
DependsBuy if you already write FFmpeg commands and want zero-commitment, usage-based hosting with n8n/Make integrations.
Usage-based hosted FFmpeg, no minimum, 2GB free — great for devs, but proof is thin.
Confidence: Medium
$0.50/GB
Starting price
drops to $0.08/GB at volume
2 GB
Free tier
no credit card required
$0
Monthly minimum
vs $25/month at Rendi
Value for money
4
No monthly minimum, 2GB free, usage-based
Ease of use
4
Auto-diagnostics, n8n/Make integrations, user-friendly
Feature depth
4
Raw FFmpeg flexibility, webhooks, MCP, SDK
Security posture
2
Upstream FFmpeg zero-days; no vendor attestations found
Pros
Cons
Gotchas
- highFFmpeg upstream disclosed 21 zero-days and a RCE CVE in 2026; hosted patch cadence undisclosed⁹
- mediumPricing starts $0.50/GB up to 10 GB before volume discounts — model actual volume first¹
- mediumOne G2 review means uptime and support claims are effectively unverified¹
- lowThird-party reviewers could not parse the free-tier terms; verify before relying on 2 GB free⁷
Best for
- Devs who already write FFmpeg commands
- n8n/Make automation workflows
- Spiky or variable transcoding volume
- Low-budget side projects
Not for
- Non-technical users wanting a simple converter GUI
- Teams wanting preset-based managed encoding
- Buyers needing a proven vendor track record
- Enterprises requiring security attestations for media workloads
Pricing
Pay-as-you-go
$0.50/GB (first 10 GB)
- First 2 GB free, no credit card
- No monthly minimum
- Dedicated 16 vCPU / 32 GB instances
Volume tier
down to $0.08/GB
- Discounted rate at higher GB usage
- Same usage-based model as AWS
Security
No product-specific breaches found in sources; but upstream FFmpeg had major 2026 disclosures, including a PixelSmash RCE and 21 zero-days.
- PixelSmash RCE in FFmpeg (CVE-2026-8461)Critical remote code execution risk in FFmpeg itself; applies to any service running FFmpeg commands, including this one.⁸
- 21 FFmpeg zero-days disclosed June 2026Autonomous security agent disclosed 21 zero-days in FFmpeg; the vendor's patch cadence for its hosted engine is not published.⁹
What users say
Feedback is scarce: one 4.5/5 G2 review praises raw FFmpeg flexibility, and Reddit users occasionally recommend it for automation workloads.
“Very Good FFmpeg gives us the flexibility of raw FFmpeg without having to ru…”
“Very Good FFmpeg is stronger for variable usage”
“For your worker problem, Very Good FFmpeg might suit…”
Alternatives
Compare Very Good FFmpeg with each alternative.
Rendi
Hosted FFmpeg API with $25/month minimum, per-byte pricing.
Very Good FFmpeg vs RendiMux
Managed video encoding and playback, no FFmpeg knowledge needed.
Very Good FFmpeg vs MuxCloudinary
Media API with transcoding plus broader asset management.
Local FFmpeg
Free; run the CLI yourself if volume is low.
Very Good FFmpeg vs Local FFmpegFull analysis
Based on ~14 public sources. Thin third-party depth: only 1 verified G2 review, and several comparison articles are vendor-authored.
Sources
review
- Rendi Pricing (2026): Pick by Bytes | Omid Saffariomidsaffari.comreview
- RenderIO FFmpeg API Pricing | Omid Saffariomidsaffari.comreview
- Very Good FFmpeg — Cloud Hosted FFmpeg REST APIverygoodffmpeg.comofficial
official
- Free FFmpeg API options compared | Rendobarrendobar.comreview
- FFmpeg Critical PixelSmash RCE CVE | LinuxSecuritylinuxsecurity.comsecurity
- 21 Zero-Days in FFmpeg | DepthFirstdepthfirst.comsecurity
- Very Good FFmpeg Alternatives | AlternativeToalternativeto.netreview
Rate this review
Anonymous. You can change your vote.
Loading votes…
Ask a follow-up
Ask if a use case fits. Answers stay inside this report and its sources.
Comments
One queue. No replies. Give a display name first. Limit: 7 comments per day.
No comments yet.