How to Erase External Drives Without Recovery
RedKey USBShare
An external drive leaving your control can carry far more than old files. It may contain employee records, customer data, financial documents, system backups, credential files, or regulated information that was copied there years ago and forgotten. Knowing how to erase external drives correctly is therefore not a formatting task. It is a data sanitisation decision that must stand up to recovery attempts, internal policy, and compliance review.
A drive that appears empty may still hold recoverable data. Before an external hard drive, SSD, USB flash drive, or removable storage device is reused, returned, resold, or disposed of, the organisation needs a repeatable process that permanently removes that information.
How do you wipe an external hard drive?
Connect the drive, confirm you have selected the right device, and erase the whole drive with a method suited to it: a full overwrite for a hard drive, or a drive-supported sanitise or secure erase command for an external SSD. Then check the result and keep a record. Formatting alone does not erase the data.
How do you wipe an external SSD?
Use the drive's own sanitise or secure erase function where the enclosure passes it through, or cryptographic erase if the drive encrypted all data from the start. Overwriting an external SSD cannot reliably reach every flash cell because of wear levelling.
Does formatting a USB drive wipe it?
No. A quick format leaves the data in place, and even a full format is not a verified sanitisation method. Erase the whole drive with a suitable method instead.
Quick formatting removes the file system’s index, not the underlying data. The operating system treats the space as available for new files, but recovery software may still reconstruct documents until the sectors are overwritten. Deleting files and emptying the Recycle Bin creates the same problem.
A full format can write across portions of a drive, depending on the operating system and device type, but it is not a substitute for a defined sanitisation process. It may not address hidden partitions, remapped sectors, device-specific behaviour, or the audit evidence an organisation needs.
For business use, the standard should be simple: if the drive held sensitive data, use a purpose-built erasure method that is appropriate for the media and produces a verifiable result. The goal is not to make data inconvenient to find. The goal is to make recovery infeasible.
Start with the drive type and its intended destination
The correct erasure method depends on what the drive is and what will happen to it next. A traditional external hard disk drive stores data on magnetic platters. An external SSD or flash drive stores data in NAND memory and uses wear levelling, which means data may be placed in locations the operating system cannot directly address. Those differences matter.
If a working drive will be redeployed internally, a verified software wipe may be appropriate. If the device is being sold or transferred to another party, the process should include documented evidence of successful erasure. If a drive has failed, cannot be accessed reliably, or is leaving a tightly regulated environment, physical destruction may be the more defensible option.
Encryption changes the decision but does not eliminate it. When a drive was encrypted from the beginning and the organisation can securely destroy every encryption key, cryptographic erasure may provide a fast route to sanitisation. However, that approach depends on confirmed encryption coverage, sound key management, and confidence that no unencrypted copies exist elsewhere on the device. When those conditions are uncertain, use an approved wipe or destruction process instead.
How to erase external drives in a controlled process
Secure erasure should be handled like any other asset disposition activity: identify the device, confirm authorisation, sanitise it, validate the outcome, and retain the record. Skipping the first and last stages creates avoidable risk.
1. Identify the correct device
Connect only the drive or drives approved for erasure whenever possible. Record the manufacturer, model, capacity, serial number, asset tag, and assigned owner or department. This prevents an operator from wiping the wrong device and ties the result to a specific asset.
Check for multiple partitions and mounted volumes. External drives often contain recovery partitions, backup volumes, or hidden areas that users do not see in File Explorer. A proper erasure workflow should address the whole physical drive, not merely a visible folder or partition.
2. Preserve anything subject to retention requirements
Confirm that the organisation has no legal hold, regulatory retention obligation, active investigation, or business need for the data. If retention is required, transfer the necessary records to an approved repository before wiping the device. Do not treat a backup drive as disposable simply because it is old. Its contents may be the only remaining copy of critical information.
Authorisation should be explicit, particularly for employee devices, client media, and drives from regulated departments. A documented approval protects both the organisation and the technician performing the work.
3. Use an erasure method designed for the media
For conventional hard drives, a software-based overwrite method can sanitise accessible sectors when it is performed and verified by a trusted tool. Multiple-pass overwriting is not automatically better for every situation. Modern guidance generally emphasises using an appropriate method and validating completion rather than applying unnecessary passes that consume time without materially improving the result.
For SSDs and flash-based external drives, generic overwrite routines can be less reliable because wear levelling may leave data in blocks that are no longer exposed to the host system. A supported sanitise command, secure erase function, or cryptographic erase process may be more suitable, provided the device supports it and the tool can execute and verify it correctly.
This is where a bootable erasure environment has a practical advantage. It can operate independently of the installed operating system and reduce interference from active processes, mounted files, or user permissions. We designed RedKey USB for this type of controlled workflow, supporting repeatable data destruction without per-device wipe limits or recurring subscription costs.
4. Do not interrupt the wipe
Keep the drive connected to stable power and avoid disconnecting the cable during the process. External drives are vulnerable to accidental interruption, especially portable USB devices powered through a laptop port. A failed or incomplete wipe must be treated as incomplete, even if most of the process ran successfully.
For high-volume work, use a dedicated workstation, labelled cables, and a check-in/check-out procedure. These operational controls are not bureaucracy. They reduce drive mix-ups and make it easier to show where each asset was at every stage.
5. Verify completion and retain the evidence
A completed progress bar is not sufficient evidence on its own. The erasure tool should report whether the selected method completed successfully and whether verification passed. Capture the result in an erasure report that identifies the drive, the method used, the date and time, and the operator or system performing the action.
This documentation is especially valuable for organisations aligning their media sanitisation programme with NIST guidance, IEEE requirements, GDPR obligations, HIPAA safeguards, contractual commitments, or internal security policy. Compliance is not only about choosing a strong method. It is about demonstrating that the method was applied to the correct asset and completed as required.
Common errors that leave data at risk
The most common mistake is assuming deletion equals destruction. It does not. Another is wiping only the active partition while leaving recovery, diagnostic, or hidden partitions intact.
Teams also create risk when they use one procedure for every device. HDDs, SSDs, encrypted drives, failed media, and removable flash devices do not always require the same treatment. A method that is reasonable for a functioning magnetic drive may be unsuitable for a damaged SSD.
Finally, do not overlook the chain of custody. An erased drive can still create an audit problem if nobody can show who authorised its disposal, where it was stored, or which serial number was sanitised. The record should follow the asset from collection through redeployment, resale, recycling, or destruction.
When physical destruction is the better choice
Software erasure is efficient when the device is functional and can communicate consistently with the wiping environment. Physical destruction becomes the stronger option when a drive is damaged, inaccessible, failed, unsupported, or too sensitive to release after software sanitisation.
Destruction should be performed through an approved process that renders the storage media unreadable. For hard drives, this may mean degaussing with equipment rated for the drive’s coercivity, or physical destruction to an approved standard. For SSDs and flash media, degaussing has no effect. If destruction is required, use disintegration or incineration, or shred only to a particle size your policy approves for that sensitivity of data.
Document physical destruction with the same discipline used for software wipes. Record the asset identifier, date, method, provider if applicable, and certificate of destruction. A pile of broken devices is not an audit trail.
Build erasure into the asset lifecycle
The safest time to decide how a drive will be erased is before it reaches a disposal bin. Establish an approved media sanitisation policy, assign responsibility, define methods by device type and data classification, and require verification records. Then train technicians to follow the same process during refresh cycles, employee offboarding, storage cleanup, and IT asset disposition.
A secure erase process protects more than the data on one external drive. It protects the organisation from a preventable disclosure, gives IT teams a defensible operational record, and turns end-of-life hardware into a controlled security event rather than an unknown risk.
Frequently asked questions
Can I erase an external drive from a bootable USB tool?
Yes, if the tool detects the external drive when the computer boots from it. Disconnect any drive you want to keep before starting.
How do I destroy a USB stick securely?
Erase it first if it still works, then, if destruction is required, use a service that reduces it to small particles (NCSC guidance for OFFICIAL data is 6 mm or less). Snapping a stick in half can leave the memory chip intact.
What should I do if I lose a USB drive with company data on it?
Report it to your IT or security team straight away, record what data it held, and assess whether it is a personal data breach. Under UK GDPR, a reportable breach must be notified to the ICO within 72 hours of becoming aware of it.
RedKey USB Home can erase connected disks alongside the internal drive, with up to 16 disks per computer. Related reading: Is Overwriting SSDs Safe? and How to Verify Hard Drive Wiping Before Disposal.