Skip to content
Bitpute

GPU guide

L40S for AI: what it actually runs

By Bitpute · Published 12 July 2026 · Updated 24 July 2026 · Specs verified against manufacturer datasheets 24 July 2026 · How we estimate · Sources · Editorial policy · Version history · Report an error · NVIDIA L40S datasheet

In short

48 GB VRAM 864 GB/s bandwidth 350 W TDP datacenter

The rentable 48 GB workhorse. The L40S is what many clouds actually rack when a job needs more than 24 GB but doesn't justify an H100 — same 48 GB tier as the A6000, newer Ada silicon, a bit more bandwidth at 864 GB/s.

AI suitability

Its fit list matches the A6000's, including Llama 3.3 70B at Q4_K_M on the same razor-thin margin. If you are choosing what to rent rather than what to buy, this is usually the cheapest hourly path to a single-card 70B.

For LLM inference the number that matters most is memory bandwidth, because generating each token means reading the whole model. On the L40S that puts the theoretical ceiling around 177 tokens/second on Llama 3.1 8B at Q4_K_M, and about 20 tokens/second on the biggest model it comfortably holds, Llama 3.3 70B — real-world throughput lands below these ceilings. At Q4_K_M with an 8K context this card comfortably fits 11 of the 12 models in our database; at the near-lossless Q8_0, 10.

Which models fit the L40S?

Computed at an 8K context (or the model's own cap). ✓ fits comfortably (≤95% of 48 GB) · ~ tight · ✗ doesn't fit. Every model links to its own guide.

ModelQ4_K_MQ8_0
Llama 3.2 1B1.7 GB 2.3 GB
Llama 3.2 3B3.5 GB 5.0 GB
Mistral 7B6.0 GB 9.3 GB
Qwen2.5 7B5.7 GB 9.1 GB
Llama 3.1 8B6.5 GB 10.1 GB
Gemma 2 9B8.9 GB 13.0 GB
Qwen2.5 14B11.0 GB 17.6 GB
Gemma 2 27B19.8 GB 31.9 GB
Qwen2.5 32B22.2 GB 36.8 GB
DeepSeek-R1 32B22.2 GB 36.8 GB
Llama 3.3 70B45.1 GB 76.6 GB
Qwen2.5 72B46.3 GB ~78.8 GB

Electricity

The board is rated at 350 W. Run it under sustained load 8 hours a day and that's about 84 kWh a month — roughly $10/month at an example rate of $0.12/kWh (set your own tariff in the workspace). Idle and light chat draw far less; the figure above is the worst case, not the typical bill.

Renting instead of buying

This is a cloud-native card — the L40S is something you rent far more often than you buy. Hourly rates move constantly, so we don't print them here; the workspace holds the current figures and shows rental cost against electricity for any model you pick.

Alternatives

A100 40GB

40 GB · 1555 GB/s · 400 W

Step down — keeps most small models, saves money and watts.

See this card →
RTX A6000

48 GB · 768 GB/s · 300 W

Same memory tier — the fit list is identical; bandwidth and price decide.

See this card →
H100 80GB

80 GB · 3350 GB/s · 700 W

Step up — the next memory tier and what it unlocks.

See this card →

Compare any two of these head-to-head — speed on the same model, cost, power — in GPU Compare.

← RTX A6000 · All GPUs · A100 40GB →

L40S in the Bitpute graph

Everything this card connects to — models it runs, where to rent it, when we recommend it, and its nearest rivals. Derived from the same data as the calculators; reviewed July 2026.

Runs these models

Largest fits at Q4_K_M (of 460 that fit):

Qwen 2 VL 72B InstructQwen 2.5 VL 72B InstructMolmo 72BQwen 2 72BQwen 2.5 72B

Even at FP16 (369 fit):

Codestral 22B v0.1Mistral Small 22B (2409) InstructERNIE 4.5 21B-A3B InstructBrowse all 506 model profiles →

Weights + overhead only; KV cache comes on top.

Rent it in the cloud

10 providers stock this class of card:

Vast.aiNebiusHyperstack (NexGen Cloud)RunPodTensorDockCrusoeCoreWeaveModal

Typically cheapest tier: Vast.ai. On-demand this card runs about $0.95/hr.

Compare all 18 providers →

When we recommend it

This card never tops an award category — a neighbour beats it on price, bandwidth or power at every requirement size. It can still be the right buy at the right street price.

Run your own numbers →

Why bandwidth matters more than core count for token generation: memory bandwidth explained.

Capacity against speed

The two axes are independent. Position on the horizontal decides which models fit; position on the vertical decides how fast they decode once they do. Note that RTX 3090 sits above it: less VRAM, more bandwidth.

VRAM against memory bandwidth, L40S highlightedScatter plot of the 12 GPUs in our set, VRAM on the horizontal axis against memory bandwidth on the vertical. L40S sits at 48 GB and 864 GB/s.01296259238885184VRAM (GB) →Bandwidth (GB/s) →122448141L40S

If a model will not load on this card

In rough order of likelihood. For reference, the largest model in our catalogue that fits this card at Q4_K_M is Qwen 2 VL 72B Instruct at 44.3 GB.

  1. The model is larger than usable VRAM, not nameplate VRAM. This card reports 48 GB but roughly 45.6 GB is available to a model after the display buffer, driver and CUDA context. A model sized against the nameplate figure will appear to fit and then fail.
  2. KV cache grew past the headroom. Weights are fixed; the cache is not. A load that succeeds at 2K context can fail at 32K on the same card, because the cache comes out of the same budget. If it loaded yesterday and fails today, context length is the first thing to check. See KV cache.
  3. The quantization is heavier than assumed. Q4_K_M is roughly 4.85 bits per weight, not 4. On a large model that difference is gigabytes. Confirm which file you actually downloaded — see which quantization to run.
  4. Something else is already holding VRAM. A browser with hardware acceleration, another model still resident, or a previous process that did not release memory. On Linux nvidia-smi shows what is allocated.
  5. It loaded but generation is very slow. That usually means layers were offloaded to system RAM rather than the load failing outright. The model runs, but every offloaded layer crosses PCIe on each token. Reduce context, drop a quantization level, or use a card with more VRAM.

Common questions

Is the L40S good for AI and local LLMs?

Yes, within its tier: with 48 GB of VRAM and 864 GB/s of memory bandwidth it comfortably runs 11 of the 12 models in our database at Q4_K_M with an 8K context, the largest being Llama 3.3 70B. Memory bandwidth caps generation speed at roughly 177 tokens/second on an 8B model in theory, with real-world results lower.

What is the biggest model an L40S can run?

Llama 3.3 70B at Q4_K_M with an 8K context is the largest comfortable fit (45.1 GB of 48 GB). Larger models need a bigger card or a multi-GPU split.

How much electricity does an L40S use?

The board is rated at 350 W. Under sustained load for 8 hours a day that is about 84 kWh a month — roughly $10/month at an example rate of $0.12/kWh. Idle draw is far lower, so light interactive use costs much less.

Data centre cards, ranked by VRAM

Server GPUs: HBM bandwidth, NVLink, MIG partitioning, rack thermals. Every card in this tier, smallest memory first — the one you are reading is highlighted. Cards shown without a memory figure are not in our calculation engine yet.

A100 40GB40 GBL40S48 GBA100 80GB80 GBH100 80GB80 GBH200 141GB141 GB

Where it sits in the stack

The L40S is an Ada Lovelace-generation part with GDDR6 with ECC memory and 4th-generation Tensor Cores. GDDR keeps the card affordable but caps bandwidth well below the HBM used in datacentre cards — and bandwidth, not core count, is what sets decode speed once a model fits.

It has no NVLink. Multiple cards talk over PCIe 4.0 instead, routed through the CPU, so splitting one model across two of these costs noticeably more than it would on an NVLink pair. Two cards each holding their own model is the friendlier pattern here.

Its Tensor Cores handle FP16, BF16, INT8 and FP8. FP8 halves activation memory against FP16 where a runtime supports it; Ampere cards do not have it. Most local inference runs weights at 4-6 bits via GGUF quantization rather than a native Tensor Core format, so these matter most for training and for server runtimes such as TensorRT-LLM and vLLM.

Its Tensor Cores support FP8, useful where a runtime can exploit it. None of this changes the VRAM arithmetic on this page — weights and KV cache still have to fit.

On the software side it is a CUDA device like any other NVIDIA card, so PyTorch, TensorRT, vLLM, llama.cpp and Ollama all run on it unchanged. What differs between cards is not compatibility but how much fits and how fast it decodes — which is what the numbers above measure. For the quantization formats these runtimes expect, and how much room the GPU Memory Calculator says you have left, start there.

Head to head

Pre-computed comparisons against the cards it is usually weighed against:

A100 40GB vs L40SRTX 5090 vs L40SRTX A6000 vs L40S