fal
the default, and the only one with a media catalogue this deep
verdictthe most complete media catalogue with per-output pricing printed on every model page — you pay a visible aggregator markup for it, and your credits expire.
- best for
- teams shipping an image or video feature who want the widest model choice and the least thinking
- price
- $0.025 / megapixel for flux.1 [dev]
- pricing note
- per-output pricing on model apis; custom deployments are billed per gpu-hour, with h100 listed at $1.89/hr. purchased credits expire 365 days from purchase and promotional credits in 90
- free tier
- no
- flux.1 [dev]
- $0.025 / megapixel
- billing
- per output; per gpu-hour for deployments
- catalogue
- 1,000+ media models
- llms too
- no — media only
- mcp server
- none published
fal carries over a thousand image, video, audio and 3d models, and prices each one on its own page in the unit that model is actually billed in. that sounds mundane until you compare it with the rest of this list, where the same question takes three page loads and often has no answer. per megapixel for images, per second for video, printed where you are already standing.
the catalogue is the reason to be here. when a new model lands, fal usually has it within days, and our image and video rankings lean on fal model pages for pricing more than any other source because those pages are the ones that exist. for a team that wants to try seedream against nano banana against flux this afternoon, nothing else is close.
the markup is real and we have measured it elsewhere on this site: routing google's models through fal costs roughly 12 to 25 percent more than going direct to the gemini api, and google's 50 percent batch pricing is not exposed through aggregators at all. on black forest labs models fal matches direct pricing exactly, so the markup is a per-vendor question rather than a flat tax, but on the google family it is the largest single line item in a heavy pipeline.
two things to know before you commit budget. fal does not serve text models, so if you want one api across generation and reasoning this is not it. and the billing terms have edges: server errors are never charged, but a 422 client error can still be billed if a runner spent gpu time before the error surfaced, and on at least one model page — Grok Imagine — fal states that generations refused for policy violations are charged anyway. credits also expire, at 365 days for purchased and 90 for promotional, which is a term most of this category does not impose.
- +over a thousand media models, and new releases land fast
- +per-output price printed on every individual model page
- +matches black forest labs direct pricing with no markup
- +the de facto reference other platforms are compared against
- −roughly 12-25% markup on google models versus going direct
- −media only — no text or reasoning models
- −purchased credits expire after 365 days, promotional after 90
- −422 errors can still be billed when gpu time was spent, and one model page states policy refusals are charged