Most-flexible AI video model means most published aspect ratios
The /best query sorts generators by supports_aspect_ratios.length, not by 'does everything well'.
The most-flexible AI video model query sorts generators by supports_aspect_ratios.length, not by "does everything well." Flexible, on that page, is a count of published ratios. It is not a quality score, not a duration ceiling, and not a verdict on prompting.
If you arrived looking for the model that will handle any brief, you are on the wrong ranking. If you arrived because the same generation has to ship to TikTok, YouTube, and a landscape site, the count is the honest signal.
Length of the aspect list
The filter is the same generator gate as the rest of the video /best tables: isVideoGenerator, plus a non-empty supports_aspect_ratios array. Utilities — removers, upscalers, extenders — drop out. Rows that generate video but publish no ratio list also drop out. What remains is sorted by array length, descending. Ties break with rankThenCost: better leaderboard position, then cheaper complete job, then name.
The spec column prints the count and the list: 8 (21:9, 16:9, 4:3, 1:1, 3:4, 9:16, adaptive, auto). That parenthetical is the whole claim. The page does not infer extra ratios. It does not collapse adaptive and auto into "smart." If those tokens are in the catalog array, they increment the length. A model with six named social ratios and no auto loses to a model with six named ratios plus auto plus adaptive, even if you will never send those two tokens.
That is methodology, not a slight. The ranking cannot see "will this look good at 9:16." It can see how many strings the catalog published. Treat the live table as the count. This post will not freeze a winner.
The aspect ratio calculator is the other half of the job: given a ratio, solve the missing pixel dimension, and copy a standard size that is actually even. Codecs encode in blocks. An odd width from naive arithmetic is a perfectly good number that a perfectly good encoder then rejects.
Eight published ratios is the current top
In the current published set, several generators sit at eight. Seedance 2.5 lists 21:9, 16:9, 4:3, 1:1, 3:4, 9:16, plus adaptive and auto. Seedance 2.0 shares those tokens. Pixverse V6 text-to-video publishes eight named ratios with no auto. Flux 3 text-to-video publishes eight including 2:1 and auto. Seven-ratio rows follow. At the other end, generators with ratio data can publish only two — usually 16:9 and 9:16. Two is enough if those are the only placements you have. It is not "flexible" under this query's definition, and the table will say so by putting them last.
Do not invent a ninth ratio and assume the model will take it. The generate schema is the list. The best square query is the other shape: filter to generators that include 1:1, then rank by leaderboard position. Presence of a ratio, not count of ratios. Use that when the placement is square and you care who is good at video, not who has the longest menu.
Flexible is not "best"
A long aspect list does not mean native audio, 4K, a 30-second take, or a face that holds. It does not mean the model is cheap. PrunaAI P-Video publishes seven ratios and a 2-credit complete-job floor; Flux 3 publishes eight and a much larger bill. The flexible ranking does not sort on credits. The cheapest-generate ranking does not sort on ratios. Mixing those knobs is how a format menu gets blamed for a look it did not rank.
It also does not mean "does everything well." There is no catalog field for that sentence. Queries the data cannot honestly answer are simply not in best.ts. Product, UGC, b-roll, and animation fit are not distinct columns. Building them would re-sort the same list under an invented label.
If matching last month's ad matters, pin the generate model in the brief and pick a ratio that row actually lists. If you are exploring which row can feed three placements from one family, sort by length and then read the spec list — confirm 9:16, 16:9, and 1:1 are in the list, not merely that the count is eight. 2:1 and adaptive pad a count without covering a Shorts slot.
The best hub is the rest of the methodology pages. This one is only the length sort.
Posting plan versus ratio count
Work backwards from the placements, then use the count as a filter. TikTok / Reels / Shorts want 9:16 at 1080×1920. YouTube landscape wants 16:9. Instagram feed and many ads want 1:1, which is why the square query exists. Cinema-adjacent work wants 21:9.
A model that publishes all four named ratios plus extras will rank high here. A cinematic 16:9-only row will not, and should not. Run the cinematic row when the job is a landscape plate. Run the eight-ratio row when the job is one family across a pack. The calculator solves the missing pixel dimension after you have picked the ratio. It does not expand the model's menu.
FAQ
Does most flexible mean best quality?
No. It means the longest published supports_aspect_ratios list among video generators that have ratio data. Quality rankings use leaderboard position. This page uses a length.
What if two models have the same count?
The tiebreak is rankThenCost: best leaderboard position, then cheapest complete job, then name. Eight and eight is not a coin flip.
Why isn't a 16:9-only cinematic model at the top?
Because it published one ratio. The query is format menu size, not cinematic merit. Use it when you need many placements from one family. Use a quality or platform query when the placement is already chosen.
How do I pick a ratio for TikTok versus YouTube?
9:16 at 1080×1920 for TikTok, Reels, and Shorts. 16:9 for YouTube landscape. Confirm the model lists that token before you generate. The calculator solves the other pixel dimension; it does not expand the model's menu.