← Back to the catalog

Water or Fire Damage

Water or fire damage sounds like the worst-case scenario in this catalog, and sometimes it is. More often, though, the platters or flash chips inside are better protected than the case around them suggests. The immediate risk is not simply that the device is wet: contamination can remain after visible moisture is gone, and applying power before the device is properly assessed or cleaned can add electrical and electrochemical damage.

Recovery decision

Water or fire damage: what should you do next?

Answer one question about the current state. The result suggests the safer next step rather than diagnosing the failure.

Typical source stabilityUnknown

Default action riskCritical

Default first actionKeep powered off

Check my situation

This guide classifies the next recovery action from observable information. It does not diagnose hardware condition or estimate a percentage chance of recovery.

What's actually happening

Water and fire damage a drive through more than one mechanism at once, and the details matter. Liquid becomes electrically dangerous when moisture, ionic or other contamination, and a voltage bias are all present together — that combination is what drives leakage, shorting, corrosion or electrochemical migration on a circuit board, not moisture by itself. Not every liquid reaches every one of those mechanisms, and how much of it reaches the recording media itself depends on the specific drive's construction. With fire, direct flame or severe heat reaching the recording assembly represents an especially serious case because mechanical, electronic and media damage can occur together; actual data survival depends on the extent and duration of the exposure. A fire incident far more often combines heat, smoke, soot and firefighting liquid — several partial mechanisms acting together rather than one clean cause — with the electronics and case typically taking the earliest and heaviest damage.

How recoverable this really is

For liquid damage, the outcome depends on the device, the liquid, contamination, corrosion, and whether power was applied. The important universal rule is not to power the device or improvise household drying or cleaning procedures. For fire damage, recoverability depends heavily on heat, deformation, soot, water used during firefighting, and whether the recording media itself was damaged.

Keep the device unpowered, record what happened and avoid cleaning methods that can move contamination into connectors or sealed assemblies. Do not heat, freeze, rinse, charge or repeatedly test it. Preserve removable cards, power supplies and associated hardware separately and tell a recovery lab what liquid, heat or firefighting exposure occurred; that history can affect how the device is handled.

What to preserve

Keep the affected device unpowered and preserve it in the condition in which it was found. Record as much of the incident history as you can — this is diagnostic context a lab needs, not bureaucracy:

• whether the device was powered during or after the exposure;
• the liquid or source involved, if known — clean water, salt or flood water, sewage, sugary or chemical liquid, or fire-suppressant residue;
• roughly how long the exposure lasted, and how close the device was to heat or open flame;
• any cleaning or drying already attempted;
• the enclosure, adapter or other original hardware associated with the device.

Retain those associated components when practical rather than discarding them.

Different media fail differently

For an HDD, the priority is preventing further mechanical or internal contamination damage; opening the HDD's internal head-disk assembly outside an appropriate controlled environment can make matters worse. For SSDs, memory cards and USB flash devices, controller and board damage may coexist with intact NAND, but modern translation, ECC, scrambling and encryption can make raw-chip access insufficient on its own. A damaged phone adds another layer because device-specific encryption may require repair of the original electronics far enough to regain normal decryption.

The general approach

Disconnect power, avoid opening a hard drive outside an appropriate controlled environment, and transport liquid- or fire-damaged media for professional evaluation without trying to boot, heat, freeze, rinse, or repeatedly test it. Handling requirements differ between hard drives, SSDs, phones, memory cards, and other devices, so preserving the device as received is safer than applying a universal wet/dry treatment.

Why "it looks dry" does not mean it is safe to power

Liquid exposure can leave conductive, ionic, corrosive or otherwise harmful contamination on electronics and connectors. Drying can remove visible moisture while leaving that residue behind. Applying power before the device has been properly assessed or cleaned can create or accelerate leakage, shorts, corrosion and electrochemical migration. The appropriate handling depends on the device and the liquid involved.

The type of contamination changes what a lab does first

“Water damage” ranges from relatively clean fresh water to salt or flood water, sewage, sugary or chemical liquids and firefighting residue — and they are not equivalent. Salt and flood water carry more aggressive corrosion potential; sugary liquids leave their own sticky contamination; fire incidents can combine several of these with heat, smoke and soot at once, so the visible exterior is a poor measure of what actually happened inside the storage device. See water, fire and contaminated-drive recovery for how each contamination type is handled differently.

Cleanroom work here is inspection as much as cleaning

HDD construction is not all the same — conventional air-filled drives typically use a filtered pressure-equalization path, while some newer drives are hermetically sealed helium designs, so how much contamination risk actually reaches the internal recording chamber depends on the specific drive and the exposure, not on a universal "sealed" property. Where contamination has reached that chamber, cleaning and inspecting the platters happens under the same particle-controlled conditions as any other internal HDD work — see cleanroom head replacement and donor matching. What's found during that inspection, not just the visible exterior damage, is what actually determines the recovery plan.

Fire damage is heat, soot, water and electronics together

A fire incident rarely damages a drive through only one mechanism. Heat and deformation, smoke and soot, and water or chemical suppressant used to fight the fire can all affect the same device at once — which is why the visible exterior gives a poor read on what actually happened to the electronics and media inside. Smoke and soot deposits can increase leakage or conductivity, and some fire residues can contribute to corrosion, but the actual effect depends on the combustion products, how they settled, and the circuit conditions underneath — it is not a fixed property of soot in general. Severe heat can also make a drive mechanically or electronically unrecoverable on its own — through lubrication, adhesives, plastics, heads, spindle or actuator tolerances, electronics, seals or enclosure geometry failing — well before there is any basis for a claim about what happened to the recording surface itself.

Like the other physical-damage scenarios in this catalog, this is squarely on the hardware side of the software vs. hardware recovery tools line — no recovery software runs until the electronics are repaired, bypassed, or the media is safely extracted. This is also precisely the scenario the "somewhere physically separate" leg of a proper backup exists for — see Backup Drive Picks. Damage this physical is squarely cleanroom territory — see our directory of major physical recovery providers for labs equipped to handle it. Once the drive is stabilized, recovery still moves through the same controlled imaging process as any other unstable source.