F5-TTS TPS calculator
Each card below is assessed against this model at the context length and minimum quality you choose. Speed is an estimate for a single request, calculated from the card's memory bandwidth and the size of the model once compressed.
Calculated for this model
818 cards we hold specifications for
Smallest card that fits
Tesla C1080
4 GB · Q8_0 · 110 tok/s
Fastest card
B200
10,090 tok/s · 180 GB
Which GPUs can run F5-TTS?
Set the inputs, read the answer
A longer conversation needs more memory, which can push this model off smaller cards.
Hides cards that would only fit the model by compressing it below this point.
818 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
10,090
tok/s
6,054–16,144 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.1 GB | Q8_0 | Comfortable |
|
10,090
tok/s
6,054–16,144 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.1 GB | Q8_0 | Comfortable |
|
8,057
tok/s
4,834–12,891 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.1 GB | Q8_0 | Comfortable |
|
8,057
tok/s
4,834–12,891 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.1 GB | Q8_0 | Comfortable |
|
6,444
tok/s
3,866–10,310 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
6,168
tok/s
3,701–9,868 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.1 GB | Q8_0 | Comfortable |
|
6,168
tok/s
3,701–9,868 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.1 GB | Q8_0 | Comfortable |
|
5,903
tok/s
3,542–9,444 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.1 GB | Q8_0 | Comfortable |
|
5,239
tok/s
3,143–8,382 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
5,239
tok/s
3,143–8,382 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
5,239
tok/s
3,143–8,382 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,969
tok/s
2,982–7,951 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,238
tok/s
2,543–6,781 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,238
tok/s
2,543–6,781 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.1 GB | Q8_0 | Comfortable |
|
4,238
tok/s
2,543–6,781 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,238
tok/s
2,543–6,781 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,238
tok/s
2,543–6,781 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,227
tok/s
1,936–5,163 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.1 GB | Q8_0 | Comfortable |
|
3,227
tok/s
1,936–5,163 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,689
tok/s
1,613–4,302 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,632
tok/s
1,579–4,211 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,573
tok/s
1,544–4,117 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.1 GB | Q8_0 | Comfortable |
|
2,573
tok/s
1,544–4,117 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,573
tok/s
1,544–4,117 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.1 GB | Q8_0 | Comfortable |
|
2,573
tok/s
1,544–4,117 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
Speeds are estimates for a single request — one conversation at a time — calculated from memory bandwidth, model size and quantisation. Real throughput varies with the inference runtime and its version. Figures published by hardware vendors measure many simultaneous requests and are much higher.
On record
Full specification
Everything on record for this model. Most of it describes how it was trained rather than how it runs — useful context for judging how much work went into it, and how it compares with models built at a different scale.
Origin
Who built this model, where, and when it was published.
- Organisation
- Shanghai Jiao Tong University,University of Cambridge,Geely Automobile Research Institute (Ningbo) Company
- Organisation type
- Academia,Academia,Industry
- Country
- China, United Kingdom of Great Britain and Northern Ireland
- Published
- 15 December 2024
- Authors
- Yushen Chen, Zhikang Niu, Ziyang Ma, Keqi Deng, Chunhui Wang, Jian Zhao, Kai Yu, Xie Chen
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Speech
- Task
- Speech synthesis, Translation
Size
How large the model is and how much data it was trained on. Parameters are the figure that decides whether it fits on a given graphics card.
- Parameters
- 335.8M
- Training data
- 27,325,800,000 tokens
- Batch size
- 307,200
The F5-TTS base model has 22 layers, 16 attention heads, 1024/2048 embedding/feed-forward network (FFN) dimension for DiT; and 4 layers, 512/1024 embedding/FFN dimension for ConvNeXt V2; in total 335.8M parameters.
"Our base models are trained to 1.2M updates with a batch size of 307,200 audio frames (0.91 hours)"
Training compute
The arithmetic performed to train the model, measured in floating-point operations. It is a measure of what the training run cost, not of how fast the finished model answers you.
- Training compute
- 4.5 × 10²⁰ FLOP
- How it was established
- Hardware
312000000000000*8*168*3600*0.3 = 4.5287424e+20
The training run
What it physically took to train: which chips, how many, for how long, and what that drew from the wall.
- Training hardware
- NVIDIA A100 SXM4 80 GB
- Chips used
- 8
- Wall-clock time
- 168 hours (7 days)
- Power draw
- 6.3 kW
"over one week on 8 NVIDIA A100 80G GPUs" 7*24 = 168 h
Availability
Whether you can obtain the model and run it on your own hardware, which is what decides if any of the graphics-card figures on this page apply.
- Weights
- Open — downloadable
- Model access
- Open weights (non-commercial)
- Training code
- Open source
- Hugging Face
- SWivid
CC-BY-NC-4.0 https://huggingface.co/SWivid/F5-TTS MIT license for training code https://github.com/SWivid/F5-TTS
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Confident
Sources
Where this record came from and when it was last checked.
- Reference
- F5-TTS: A Fairytaler that Fakes Fluent and Faithful Speech with Flow Matching
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run F5-TTS
Ranked by estimated tokens per second, newest card first where speeds tie. Because generation is bound by memory bandwidth, this ordering follows bandwidth rather than any gaming benchmark.
- 01 B300 288 GB · 8,000 GB/s · Q8_0 10,090 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 10,090 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 8,057 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 8,057 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 6,444 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 6,168 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 6,168 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 5,903 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 5,239 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 5,239 tok/s
The smallest GPUs that still run F5-TTS
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 GeForce RTX 4010 4 GB · needs 1.1 GB · Q8_0 · comfortable 121 tok/s
- 02 RTX A400 4 GB · needs 1.1 GB · Q8_0 · comfortable 121 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.1 GB · Q8_0 · comfortable 161 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.1 GB · Q8_0 · comfortable 242 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.1 GB · Q8_0 · comfortable 43.0 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.1 GB · Q8_0 · comfortable 126 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.1 GB · Q8_0 · comfortable 142 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.1 GB · Q8_0 · comfortable 126 tok/s
- 09 Arc A310 4 GB · needs 1.1 GB · Q8_0 · comfortable 102 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.1 GB · Q8_0 · comfortable 105 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla C1080
Memory needed
1.1 GB
Fastest
10,090 tok/s
F5-TTS is small enough at 335.8M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The entry point is the Tesla C1080: 4 GB of memory, Q8_0 compression, roughly 110 tokens per second.
At the other end, a B200 generates roughly 10,090 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.
Background
F5-TTS was published by Shanghai Jiao Tong University,University of Cambridge,Geely Automobile Research Institute (Ningbo) Company, in China, in December 2024. The organisation is categorised as academia,Academia,Industry.
It works in Speech, and is recorded as doing speech synthesis, Translation.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. It is published under the SWivid organisation on Hugging Face.
Reading the throughput figures
The median result is around 283.3 tokens per second; 818 cards produce text faster than most people read it.
Being dense, it reads all of itself per token, which is why the ordering by speed below follows the ordering by memory bandwidth so closely.
Its internal architecture is not on file, so memory is approximated from the parameter count and marked accordingly. Expect the real figure to differ, more so at long context.
How it was trained
The training run consumed about 4.5 × 10²⁰ FLOP, on NVIDIA A100 SXM4 80 GB. That figure describes the cost of creating it and has no bearing on how quickly it generates text.
Around 27,325,800,000 tokens went into training it.
Step by step
How to choose a GPU for F5-TTS
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Check what it needs before anything else
Every card here has been checked against F5-TTS — around 1.1 GB at Q8_0. Capacity is the gate — a card either holds it or it does not.
-
02
Set the context length you will work at
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for F5-TTS.
-
03
Decide how much compression you will accept
Each card runs the least-compressed copy it can hold — Q8_0 on the smallest card that fits. Setting a floor drops the cards that only manage F5-TTS by squeezing it further than you would want.
-
04
Compare tokens per second, not specifications
Ranking by tokens per second for F5-TTS follows memory bandwidth, not core counts, which is why the B200 tops it at 10,090 tok/s.
-
05
Check the fit verdict before buying
A tight fit runs F5-TTS but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
06
Check the card from the other side
Every card name links to its own page, which runs the same calculation across the whole model catalogue. Worth a look before buying for F5-TTS alone — a card is usually bought for more than one model.
Answers
F5-TTS — common questions
How fast is F5-TTS on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 10,090 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 818 of the cards that can run F5-TTS clear that.
How much VRAM does F5-TTS need?
About 1.1 GB at Q8_0 compression, which is what the smallest card that runs it uses. Less compression needs more: the figures in the memory column above are recalculated for each card, because each one holds the least-compressed version it can.
Can I run F5-TTS on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,879 tokens per second — a comfortable fit.
Can I run F5-TTS on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,151 tokens per second — a comfortable fit.
Can I run F5-TTS on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,425 tokens per second — a comfortable fit.
Can I run F5-TTS on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,690 tokens per second — a comfortable fit.
Is F5-TTS open source?
Its weights are published, so F5-TTS can be downloaded and run on your own hardware. Note that open weights is not the same as open source in the full sense — it says nothing about the training data, the training code, or the commercial terms attached.
How many parameters does F5-TTS have?
F5-TTS has 335.8M parameters. The F5-TTS base model has 22 layers, 16 attention heads, 1024/2048 embedding/feed-forward network (FFN) dimension for DiT; and 4 layers, 512/1024 embedding/FFN dimension for ConvNeXt V2; in total 335.8M parameters. That figure is the total, and it is what decides how much memory the model needs — roughly half a gigabyte per billion at the compression most people use.
Who created F5-TTS?
F5-TTS was published by Shanghai Jiao Tong University,University of Cambridge,Geely Automobile Research Institute (Ningbo) Company, based in China, categorised as academia,Academia,Industry.
When was F5-TTS released?
F5-TTS was published in December 2024. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
What is F5-TTS used for?
F5-TTS works in Speech, and is recorded as handling speech synthesis, Translation. A model can carry several of each, so these are the areas it was built for rather than a limit on what it will attempt.
Where can I download F5-TTS?
Its weights are published under the SWivid organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.
How much compute was used to train F5-TTS?
Around 4.5 × 10²⁰ FLOP, on NVIDIA A100 SXM4 80 GB. That measures what producing the model cost and says nothing about how quickly it answers once trained — inference speed comes from memory bandwidth, not from the training budget.
Can I run F5-TTS if it does not fit in my GPU?
It can be split between the card and system memory, but F5-TTS generates painfully slowly that way. Nothing on this page assumes offloading.
Would two GPUs run F5-TTS faster?
Capacity adds across cards; throughput does not. Since 818 of the cards we track already hold F5-TTS on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for F5-TTS?
Each card is shown running the least-compressed copy it can hold, and F5-TTS appears at 1 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these F5-TTS speed estimates?
They are calculated from specifications rather than measured, and each carries a range — 6,054–16,144 tok/s on the B200, for instance. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
What GPU do I need to run F5-TTS?
The smallest card in our catalogue that holds F5-TTS is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.1 GB, and produces roughly 110 tokens per second. 818 cards in total can run it.
The other direction
Looking at it from the other side?
This page starts from the model. If you already own a card and want to know everything it will run, start from the hardware instead.