balenaEtcher
A focused cross-platform utility for writing operating-system images to USB drives and SD cards, with verification and removable-media checks.
What balenaEtcher is for
balenaEtcher writes an operating-system image to a USB drive or SD card and can verify the result. Its simple workflow is useful for installation media, recovery media and test devices, but the target drive is overwritten. The image, target capacity and removable-media identity should be checked before writing.
Treat the target device as destructive
Selecting the wrong disk can erase personal data. Disconnect unrelated removable drives, compare the displayed name and capacity with the physical device and keep the original image in a known location. Verification checks the written result; it does not recover files that were already overwritten.
Keep images and recovery notes
Store images, checksums, device labels and the purpose of each boot medium together. If a device will be reused, erase or repartition it through the operating system after confirming that no recovery data is needed.
Maintenance note
This page reviews balenaEtcher image writing, removable-media selection, verification and recovery boundaries. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave balenaEtcher to this cloud drive
Baidu Netdisk
Save balenaEtcher to this cloud drive
balenaEtcher image writing and verification
Use a spare removable drive, confirm the image and target three times, write a small test image first when practical, and verify the result before booting.
Before you start
- Back up important files and disconnect removable drives that are not part of the task.
- Prepare a complete image file and record its expected size and checksum when available.
- Use a target device with enough capacity and a reader or port that is stable during writing.
Installation steps
- 01
Install the matching application
Install the package for the operating system, launch it and grant only the removable-media permission required for the write operation.
- 02
Select the image
Choose the intended image file, confirm its name and size, and keep a separate copy until the new medium has booted successfully.
- 03
Select the target carefully
Compare the device label, capacity and connection with the physical drive, then remove unrelated removable media before proceeding.
Quick start
- 01
Write the image
Start the write and avoid disconnecting the drive, suspending the computer or launching another disk utility until the operation completes.
- 02
Verify the result
Let verification finish, review errors and repeat with a different port or reader only after confirming that the image and target are correct.
- 03
Label and test the medium
Record the image version and purpose, eject safely and test the medium on the intended machine without overwriting the source image.
Usage tips
- Never select a system or backup disk merely because its capacity looks similar to the target.
- Keep a checksum and image version with the device so a failed boot can be separated from a bad write.
- A successful write does not prove that the target hardware will boot in every firmware mode.
Troubleshooting and uninstall
Why does the target drive not appear?
Check the cable, reader, operating-system permissions and device health, then reconnect only the intended removable drive and refresh the list.
Why does verification fail?
Compare the image checksum and target capacity, try a stable port or reader and inspect the drive for errors before repeating the write.
- Preserve images and notesKeep the source image, checksum and device purpose if the medium may be needed again.
- Remove the applicationUninstall through the operating system and clear temporary image files only after confirming that the boot medium and backup are usable.
Frequently asked questions
Will writing an image preserve files already on the USB drive?
The target is normally overwritten. Back up any required data and verify the selected device before starting.
Does verification repair a bad removable drive?
No. Verification compares the written result with the image. It can reveal a bad write or failing media but does not restore overwritten data.
Why can a verified medium still fail to boot?
Firmware mode, partition layout, device compatibility and the image itself affect booting. Test the medium on the intended hardware and settings.