Data Recovery Case File · Cameras, Drones & Cards · Salt Changes Everything
Salt Water Leaves Something Behind That Keeps Working After It Dries
Her enquiry names an exposure that behaves differently from ordinary liquid. A large memory card "damaged by sea water", on which two consumer recovery packages have been run without success. Salt water is not simply wet: the water evaporates and the salt remains, conductive and corrosive, so a card that appears dry is still being attacked.
| Media | 512GB memory card following immersion in salt water — consumer recovery software run without result; content required |
| Reported situation | Memory card exposed to sea water · card subsequently not yielding content · two consumer recovery packages run against the card · neither returning files · owner seeking cost and timescale |
| Fault class | Salt contamination with ongoing corrosion — conductive residue persisting after drying; software approaches inapplicable where the device does not present |
| Equipment used | Salt residue identified as an active rather than historic exposure · no powering permitted before cleaning · residue removed and contacts and board cleaned under magnification · memory read directly at chip level where board recovery was not achievable · translation layer reconstructed in software |
The decode: why salt is worse than water, and why software could not help
What ordinary water does: conducts while present and evaporates afterwards, leaving relatively little behind. A device dried thoroughly and promptly often survives it, which is why the advice for fresh water focuses on drying.
What salt water does differently: it deposits. The water leaves and the salt stays, drawn into every gap and settled across the board — so the exposure does not end when the card looks dry.
Why that residue is actively harmful rather than merely present: salt is conductive and hygroscopic. It draws moisture from ordinary air, forming a conductive film across contacts that should be isolated from one another — which creates paths that should not exist.
Why that matters most when power is applied: corrosion requires moisture, contaminants and an electrical potential. The immersion supplied the first two permanently, and every connection supplies the third — so a powered card corrodes fast where an unpowered one corrodes slowly.
Why running recovery software was the wrong first step: every attempt required the card to be inserted and powered. Each of those was a period of active corrosion, and none of them could have succeeded, because software needs the device to present itself before any of its capability is relevant.
Why that is worth saying without reproach: reaching for software is the obvious response, and nothing about the packages suggests they would be inappropriate. The mismatch is that they solve logical problems and this is a physical one.
What has to happen before anything else: cleaning. The residue is removed and the board and contacts cleaned under magnification before any power is applied, because powering a salt-contaminated card is how a recoverable one becomes a shorted one.
Why the memory is likely to have survived: the memory component is sealed within its own packaging. Salt reaches the board, the contacts and the connections rather than the storage itself, so the content is usually intact behind damaged conductive paths.
Why the card's capacity is worth noting: a card of that size holds a great deal, and large cards use memory that stores several bits per cell. That makes direct reading more involved — it does not prevent it, but it is the reason a realistic timescale is longer than for a small card.
What must not happen: no further insertions, no more software, and no attempts to dry it with heat. Heat drives residue further into the assembly and does nothing about salt.
On the bench
Salt residue was identified as an active rather than historic exposure — water evaporating while salt remains, conductive and hygroscopic, drawing moisture from ordinary air to form conductive films across contacts that should be isolated. Corrosion requires moisture, contaminants and an electrical potential, of which the first two persist and the third is supplied by every connection. No powering was permitted before cleaning, and memory was read directly at chip level where board recovery was not achievable.
The outcome
The residue identified as active, no powering permitted before cleaning, and the memory read directly where board recovery was not achievable. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: salt water does not stop when it dries. The water leaves and the salt stays — conductive, drawing moisture from the air, and corroding fast whenever power is applied.
Anything that has been in sea water
Stop inserting it and stop running software against it — each attempt powers the card, and corrosion needs moisture, contaminants and a voltage, of which the immersion supplied two permanently and every connection supplies the third. Salt water differs from fresh in a way that matters: the water evaporates and the salt remains, conductive and drawing moisture back out of ordinary air, so the exposure continues after the card looks dry. Don't apply heat to dry it, which drives residue deeper and does nothing about salt. The memory itself is sealed and usually survives.
Stop powering it — call Manchester Data Recovery on 0161 871 0788; salt residue identified as active exposure, cleaned under magnification before any power, memory read directly at chip level.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.