← All guides

Drive Temperature: Safe Ranges for HDDs, SATA SSDs, and NVMe Drives

Guide · Published 2026-10-23 · Last updated 2026-10-23

Every drive reports its temperature, and almost nobody looks at it until something slows down. The problem with the usual advice is that it quotes one number for every kind of drive. A hard drive, a SATA SSD, and an NVMe SSD live in different thermal worlds — what is a warning sign for one is a normal working temperature for another — so the ranges have to be separated before they mean anything.

The ranges, separated by drive type

Working temperature guide by drive type
Drive typeTypical working rangeInvestigate when
Hard drive (HDD)Roughly 20-50C; most run 30-45CSustained readings above about 50C
SATA SSDCommonly 30-65C in useApproaching or exceeding 70C
NVMe SSDOften 50-70C under load is normalIdling near 55-60C, or sustained load readings climbing toward 80C+

Two cautions make these numbers honest. First, they are working guides, not specifications: the specific drive's manufacturer documentation is the authority for that model, and throttling thresholds in particular vary by drive. Second, idle and load readings answer different questions. An idle reading tells you about your case's baseline cooling. A load reading — taken during a large file copy or a backup — tells you whether the drive can shed heat when it works. A drive that idles cool and cooks under load has an airflow or heatsink problem that an idle screenshot will never show.

Throttling: the symptom that looks like failure

Modern SSDs protect themselves by slowing down. When the controller gets hot, firmware steps performance down — often gradually, across many small steps — so the slowdown arrives as a vague feeling that the machine is tired rather than a clear failure. The practical test is a sustained transfer: copy a very large file or folder between drives and watch the speed. A transfer that starts at full speed and then falls off a cliff after roughly half a minute — in one documented example, from around 5 GB/s down to 500 MB/s or lower — and stays down is the classic throttling signature. A failing drive behaves differently: errors, stalls, disappearing files, and health warnings, not a clean, repeatable speed cliff that recovers after the drive cools. Telling these two apart matters, because one is fixed with airflow and the other is fixed with a replacement and a backup.

How to check your drive's temperature

  1. NVMe on Windows 11 — no install needed. Open Settings, then System, then Storage, then Advanced storage settings, then Disks & volumes. Select the drive, open Properties, and read the Drive health section: temperature, estimated remaining life, and available spare. This panel exists for NVMe SSDs only; its absence on a SATA drive or hard drive is normal, not a fault.
  2. PowerShell, for what Windows tracks. In an administrator PowerShell, run Get-PhysicalDisk | Get-StorageReliabilityCounter and read the Temperature value where the drive reports one. Blank fields are common and are missing data, not errors.
  3. Any drive type — a monitoring tool. CrystalDiskInfo shows each drive's temperature beside its Health Status, and Libre Hardware Monitor lists drive temperatures without needing installation. Because SSDs fail silently — there are no moving parts to make warning noises — a monitoring tool running in the background is the practical way to catch a slow thermal problem, rather than checking once and forgetting.
  4. Record two numbers. Note the idle temperature after the machine has sat for ten minutes, then the temperature during a large copy. Write both down with the date; a single reading is trivia, a pair is a diagnosis, and a series is an early-warning system.

What success looks like: you can state, for each drive you own, its idle and under-load temperatures and which range row it belongs on — and any drive outside its row has a named next step (airflow, heatsink check, or replacement planning) rather than a worry.

If a drive runs hot: the fix order

Work cheapest first. Clear dust from case intakes and confirm case fans actually spin. For an NVMe drive under a motherboard heatsink, check the thermal pad: a forgotten protective peel left on the pad is a documented, common cause of a drive running far hotter than it should. Confirm the drive is not buried against a hot graphics card's exhaust with no air path. Then re-run the same sustained transfer and compare numbers — the fix is verified by the load reading falling, not by the work feeling thorough. If temperatures stay high with clean airflow and a correct heatsink, or the health status in your monitoring tool reads Caution or Bad, treat it as a drive problem: back up first, then replace. Heat plus health warnings is not a cooling project.

Laptops and external drives: the two awkward cases

Laptop drives live in a thermal compromise. The chassis has little air to spare, the drive often sits near other warm components, and readings several degrees above a desktop's are routine rather than alarming. Judge a laptop drive against its own history instead of a desktop chart: a stable pattern over months is reassurance, while a sudden step upward after no hardware change is a prompt to check for dust, a failing fan, or a background process pinning the drive at full activity. External drives in enclosures are the second awkward case. A sealed plastic enclosure is an overcoat: the drive inside commonly runs warmer than the same drive in a ventilated case, and many basic enclosures report temperature poorly or not at all through USB. If an external drive feels hot to the touch during a long backup and its software reports nothing, shorten the session into stages, give the drive air, and treat the missing sensor as a reason for caution rather than comfort. For an archive drive that is only awake during scheduled checks, a warm reading at the end of a full read is expected; the number that matters is whether it climbs steadily across successive checks.

Workload notes: when a hot reading is the workload talking

Not every high reading is a cooling failure. A drive rebuilding, verifying a large backup, or absorbing a sustained write workload is doing the heaviest work it ever does, and its temperature will peak accordingly — which is precisely why the load reading is taken then: it is the worst honest case. The distinction that matters is recovery. A healthy setup sheds heat when the workload ends, and the reading falls back toward idle within minutes. A drive that stays hot long after the work stops, or runs hotter during the same recurring backup month after month, is telling a trend story rather than a workload story, and trends are what the dated log in the checking procedure exists to catch. Small, warm-running drives inside game consoles, recorders, and network enclosures deserve the same trend treatment, since their owners rarely see a number until a monitoring tool is deliberately pointed at them.

Questions owners ask about drive temperature

Is 70 degrees dangerous for an SSD? For a SATA SSD it is the top of the comfortable range; for an NVMe under load it can be ordinary. The drive type and the idle-versus-load context decide — which is why this guide separates them.

Why does Windows show health for only one of my drives? The Settings drive-health panel covers NVMe SSDs. SATA SSDs and hard drives need a monitoring tool instead; the missing panel is a Windows limitation, not a symptom.

Can heat permanently damage a drive? Sustained overheating shortens drive life and causes throttling long before that. Treat persistent high readings as a maintenance task with a deadline, not an emergency — unless health warnings appear alongside them, in which case back up first and ask questions later.