L40S

An L40S runs 28 of the 34 open models tracked here at Q4_K_M with 8k context, computed on 16 October 2026. The largest is Qwen3.6 35B-A3B (MoE), needing 22.4 GB and generating at most 348 tokens per second.

Updated

Memory
48 GB VRAM
Bandwidth
864 GB/s
Board power
350 W
Released
2023
Availability
Rented, not bought
What it runs
28 of 34 models
At Q4_K_M with 8k context. The largest it holds is Qwen3.6 35B-A3B (MoE): 22.4 GB, at most 348 tokens per second.
Computed 16 October 2026
Best model to run
Muse Glimmer 30B
18.7 GB of 48 GB, about 35 tokens per second: comfortable for chat. Picked as the biggest class of model that fits with room to spare and answers at 25 tokens per second or faster, then the newest release in it.
Computed 16 October 2026
Rent the same card
$0.79 an hour
One L40S on RunPod Community, third-party host, on demand before tax, or $1.09 on RunPod, which runs its own data centres. Every provider compared.
Read 19 October 2026

Open the L40S in the LLM checker

What an L40S runs, model by model

L40S 48 GB addresses 48 GB at 864 GB/s. Every model below is at Q4_K_M with 8k of context, the setting most people actually use. Once the 5% safety margin comes off, the card has 45.6 GB to spend: memory decides what loads, bandwidth how fast it answers. Both are estimates from stated formulas, and the VRAM calculator shows the working.

On this card a model fits at or under 45.6 GB, and above 40.8 GB it is tight: it loads, but there is little left for the conversation, and a desktop on the same 48 GB can push it over. Tokens per second are single-stream estimates from memory bandwidth; ≤ marks a ceiling real runtimes fall well below.

Computed 16 October 2026

The model to actually run on it

Muse Glimmer 30B is the best use of this card: 18.7 GB of the 48 GB available, an estimated 35 tokens per second, comfortable for chat, and 131,072 tokens of context still available.

How this is chosen, since no benchmark is quoted: models are compared by size, a mixture-of-experts model counting at the geometric mean of its total and active parameters (a rule of thumb, not a measurement). The pick is the biggest class that fits with memory to spare and answers at 25 tokens per second or better, and within that class the most recent general-purpose release; coding and reasoning specialists are listed above but not recommended by default.

Qwen3.6 35B-A3B (MoE) is the largest model the card will hold, at 22.4 GB, with room for 131,072 tokens of context. It is a mixture-of-experts model reading only 3B parameters per token, so it is the faster of the two at an estimated 348 tokens per second; what it gives up is the depth of a dense model that reads all of its weights for every token.

It also fits at Q8_0, in about 33.5 GB, which is worth taking whenever the memory allows: Q8 is near-lossless where Q4 costs a little accuracy.

How much context actually fits

Model size is the question people ask; context is the one that bites. The KV cache grows linearly with the conversation, so a model that loads comfortably can still run out of memory halfway through a long document. On 48 GB, the context you get is whatever the weights leave behind, which is why two cards that run the same model can feel completely different in use. These are the largest contexts this card holds, at Q4_K_M weights.

ModelMax context, FP16 KVWith Q8 KV cache
Muse Glimmer 30B 131,072 tokens 131,072 tokens
Qwen3 32B 40,960 tokens · model limit 40,960 tokens · model limit
Gemma 4 31B 131,072 tokens 131,072 tokens
Granite 4.2 30B 104,448 tokens 131,072 tokens

Quantising the KV cache to Q8 roughly doubles what you can hold, at a quality cost most people never notice: Granite 4.2 30B on this card goes from 104,448 to 131,072 tokens. Capped at 128k tokens, or at the model's own native window where that is smaller, marked "model limit": free memory beyond that point buys nothing. Rows that hold far more context than their size suggests are hybrid, sliding-window or latent-attention models, which cache only a fraction of what a standard transformer does; each model page shows the working.

Computed 16 October 2026

Where this card stops

The first model out of reach is Llama 3.3 70B: about 45.8 GB at Q4_K_M and 8k context, against 48 GB of usable memory. That is close enough to be worth a caveat: it is inside the raw 48 GB and only misses the 95% line this site uses for a fit. On a card with a display attached, treat it as no. On a headless card, with a shorter context, it runs. Dropping to Q3_K_M would need about 37.7 GB, which fits, though Q3 loses enough quality that a smaller model at Q4 is usually the better trade. Offloading the remainder to system RAM works and is ten to fifty times slower; it is a way to see a model run, not a way to use one.

Buy or rent

Cheapest hour
$0.79 an hour
One L40S on RunPod Community, third-party host, on demand before tax.
Read 19 October 2026
In a data centre
$1.09 an hour
One L40S on RunPod, which runs the machine itself. On demand before tax.
Read 19 October 2026
AWS, Google Cloud or Azure
$1.86 an hour
The cheapest single L40S from the big three, on AWS. On demand before tax.
Read 19 October 2026

There is nothing to decide here: you rent it. Use it as the reference when comparing a 48 GB rental against buying an RTX 6000 Ada.

There is no purchase price to reason about, only an hourly one, and it differs by provider and by week. Put the figure you are actually looking at, with your electricity rate and your real monthly hours, into the build vs rent calculator, which already knows this card draws 350 W under load. It returns the month owning becomes cheaper, or tells you it never does. Hours per month decides it far more often than the price does.

Rented, an L40S costs from $0.79 an hour (RunPod Community, third-party host), or $1.09 from a provider that runs the machine (RunPod), on demand, before tax, read 19 October 2026. Every provider's price is in the cloud GPU price guide.

The honest take

The 48 GB card you meet as a rental line item, not as a purchase.

The L40S is the same Ada silicon family as the RTX 6000 Ada, packaged for servers: passively cooled, 350 W, no display outputs. On paper it is a slightly slower 48 GB card at 864 GB/s. In practice it is the card most cloud providers hand you when you ask for 48 GB, so its real relevance is as a price and speed reference for renting rather than a thing you install.

What it is good at

  • 48 GB comfortably holds 32B models with very long context, and brings 70B at Q4 to the edge of what fits.
  • Widely stocked by providers, so it is usually available without queueing.
  • Good for image and video generation, where its Ada compute is put to use.

What it is not

  • 864 GB/s is below the RTX 6000 Ada's 960 GB/s, on the same 48 GB.
  • Passive cooling means it only works in a chassis with forced airflow, so it cannot go in a desktop.
  • No display output, so it is an accelerator only.

The thing people get wrong: It has no fan. The card depends entirely on server chassis airflow, which is why buying one second-hand for a tower build ends badly.

Compared with the alternatives

  • RTX 6000 Ada: 48 GB · 960 GB/s · best fit Muse Glimmer 30B at ~39 tok/s. Forty-eight gigabytes in a normal computer, at 300 watts, without the noise.
  • A100: 80 GB · 2,039 GB/s · best fit Llama 3.3 70B at ~35 tok/s. The old datacenter workhorse, still fast where it counts, and cheap to rent.
  • RTX PRO 6000 Blackwell: 96 GB · 1,792 GB/s · best fit Llama 3.3 70B at ~31 tok/s. Ninety-six gigabytes and 5090-class bandwidth on one card.

All 39 cards are compared side by side on the GPU index, and the same numbers from the model's point of view are on each model fit table. To check one specific pairing rather than read a table, use the can-I-run-it checker.

Questions

Can an L40S run a 70B model?
Not at Q4_K_M in one card. Llama 3.3 70B needs about 45.8 GB at 8k context and this card can address 48 GB. Your options are a smaller model, a harsher quantisation with very little context, splitting across two cards, or renting a larger one for the hours you need it.
What is the best model to run on an L40S?
Muse Glimmer 30B. At Q4_K_M and 8k context it needs about 18.7 GB of the 48 GB available and generates an estimated 35 tokens per second, which is comfortable for chat. It also fits at Q8, at about 33.5 GB, which is worth taking when it fits.
How many tokens per second does an L40S generate?
It depends entirely on the size of the model, because generating a token means reading every active weight out of memory. At 864 GB/s and 70% efficiency, this card produces an estimated 130 tokens per second on an 8B model at Q4, and about 348 on the largest model it holds, Qwen3.6 35B-A3B (MoE). Reading speed is roughly 5 to 8 words per second, so anything above 25 feels immediate. Treat 130 as a ceiling on 864 GB/s rather than a measurement; the higher a figure, the further real runtimes fall below it.
Is 48 GB enough for running LLMs locally?
It runs 28 of the 34 models tracked here at Q4_K_M with 8k of context, up to 36B parameters. The honest test is not the model list but the context: Muse Glimmer 30B on this card holds about 131,072 tokens before memory runs out.
L40S or RTX 6000 Ada for local models?
Both address about the same memory, so they run the same models. On speed, the RTX 6000 Ada is faster: 960 GB/s against 864 GB/s, and bandwidth is what sets chat speed.
Can I put an L40S in a desktop PC?
No. It is passively cooled, with no fan on the card at all, and it depends on the forced airflow of a server chassis. Installed in a tower it will overheat. The desktop equivalent of this silicon is the RTX 6000 Ada.
L40S or A100 for inference?
The A100 has more memory and much more bandwidth, 80 GB at 2,039 GB/s against 48 GB at 864 GB/s, so it generates faster and holds larger models. The L40S has newer Ada compute, which helps with image and video generation and with prompt processing. For chatting with a large language model, the A100 is the better rental.
  • Memory: weights (parameters × bytes per parameter) + KV cache (2 × layers × KV heads × head dim × context × bytes for a standard transformer; sliding-window, hybrid and latent-attention models counted as they actually cache) + 0.5 GB runtime + 4% of weights. Full derivation in the VRAM calculator.
  • Speed: 70% × bandwidth ÷ active weight bytes, single stream, no batching, prompt processing excluded. A ceiling, not a measurement: the 12 of 28 figures marked ≤ are where real runtimes fall furthest below the number, because so few weights are read per token. See the tokens-per-second estimator.
  • Card specification (manufacturer figures): 48 GB, 864 GB/s, 350 W; see NVIDIA's own page for this card.
  • Hourly prices: each provider's own pricing page or price API, read 19 October 2026, as listed in the cloud GPU price guide.
  • Model architecture values come from each model's published config; the self-hosted LLM guide explains what each one changes.