Clone SD Card to Image: Full Guide

Updated 7 November 2026 · Standard formula, shown below

Yes, you can clone an SD card to an image file, which creates a single-file backup of the entire card, including all partitions, files, and boot data. You do this with disk-imaging software that reads the card block-by-block and writes the output to an image file, which you can later restore to the same or a different card. This guide explains the process, the tools you can use, the differences between cloning and copying, and how to avoid common pitfalls.

Why Clone to an Image Instead of Copying Files?

Copying files from an SD card to a folder on your computer only copies the visible data within the file system. It misses the boot sector, partition table, and any hidden or deleted data, and it also changes file timestamps and permissions. Cloning to an image captures every byte of the card, including the Master Boot Record (MBR) or GUID Partition Table (GPT), making it a true 1:1 snapshot. This is essential for:

Backing up a bootable operating system (like Raspberry Pi OS or a retro-gaming system).
Preserving the exact state of an embedded system or a digital camera’s card before troubleshooting.
Recovering data from a failing card (although a direct image is safer than attempting file copies).
Duplicating a card to multiple identical cards without reconfiguring each one.

How Disk Imaging Works

Disk imaging software reads the SD card as a block device, meaning it accesses the raw storage sectors directly, bypassing the file system. The software reads each sector sequentially and writes the data into a container file, often with a format like .img, .iso, or a proprietary format like .dd. The image file is not compressed by default, so its size will be roughly the same as the card’s capacity (e.g., a 32 GB card produces a ~32 GB image). Some tools offer compression to reduce file size, but that can slow down the process and is not always necessary.

When you restore the image, the software writes the data back to the card sector-by-sector, effectively replacing the entire card’s contents. This is why the destination card must be at least as large as the original (or the image size, if it’s smaller).

Choosing the Right Tool

Many free and commercial tools can clone an SD card to an image. The best choice depends on your operating system and your comfort with the command line.

Linux / macOS: The dd command is built-in and can create a raw image with a single line. It is powerful but dangerous if you mix up input and output devices.
Windows: Win32 Disk Imager is a popular open-source tool that can read an SD card and write an image. It is simple and widely used for Raspberry Pi projects.
Cross-platform: Balena Etcher is known for writing images to cards, but it also has a “clone drive” feature that can read a card and save an image. It is user-friendly and works on Windows, macOS, and Linux.
Advanced: Tools like Clonezilla or Rescuezilla offer partition-level cloning and compression, and they can also clone a card directly to another card without creating an intermediate image file.

Step-by-Step: Cloning with Win32 Disk Imager (Windows)

Insert the SD card into your computer’s card reader.
Download and run Win32 Disk Imager (you may need to right-click and select “Run as administrator”).
In the “Image File” field, click the folder icon and choose a location and filename for your image (e.g., backup.img).
In the “Device” dropdown, select the drive letter that corresponds to your SD card. Double-check this—choosing the wrong drive can overwrite your hard drive.
Click the “Read” button. This will read the entire card and save it to the image file.
Wait for the progress bar to finish. The time depends on the card size and speed.

On Linux, the equivalent dd command is:

sudo dd if=/dev/sdX of=~/backup.img bs=4M status=progress

Replace /dev/sdX with the correct device node for your card (check with lsblk). After the command finishes, run sync to ensure all data is written.

Common Mistakes and How to Avoid Them

Wrong device letter: The most critical error. On Windows, use Disk Management to identify your SD card’s capacity and drive letter. On Linux, use lsblk to see the size and mount points.
Not unmounting the card: On macOS and Linux, you must unmount the card before imaging, or the system may write cache data mid-read. On Windows, close any Explorer windows showing the card.
Card is write-protected: Some SD cards have a physical lock switch. If it’s locked, the card is read-only and you cannot clone it (though you can still read it).
Assuming the image is smaller than the card: A raw image is a full-size copy. If you want a smaller file, you need a tool that compresses or shrinks the image (like Clonezilla with compression, or using gzip on the output of dd).
Interrupting the process: If the read is interrupted, the image is corrupt. Ensure your computer has power and the card reader is stable.

Image Formats: Raw vs. Compressed vs. Partitioned

Most tools produce a raw image (a byte-for-byte copy) with an extension like .img or .dd. This is the most compatible format for restoring with tools like Etcher or Win32 Disk Imager. Some tools, like Clonezilla, use their own compressed format that can only be restored by the same tool. There is also the option to create a partition image (only one partition) instead of a whole disk image, which is useful if you only need the data partition and not the boot loader.

Restoring the Image to a New Card

Restoring is the reverse process. In Win32 Disk Imager, you select the image file and the target drive, then click “Write”. In Etcher, you select the image and the target, then click “Flash”. The destination card will be completely overwritten, so all existing data on it will be lost. After writing, safely eject the card and insert it into your device. If the device does not boot, the card may be too small, or the image may have been corrupted.

Frequently Asked Questions

Can I clone a larger SD card to a smaller image?

Yes, if the actual data on the card is less than the card’s capacity, you can shrink the image using tools like pishrink (for Raspberry Pi images) or by resizing the partition before imaging. However, a raw image will always be the full size of the card, so you must use a tool that supports shrinking or compression.

Is it better to clone to an image or clone directly to another card?

Cloning directly to another card (device-to-device) is faster because it avoids the intermediate file. However, having an image file allows you to store multiple backups, restore at any time, and share the setup. For a one-time duplication, direct cloning is fine; for ongoing backups, an image is more flexible.

Does cloning an SD card copy deleted files?

Yes, a raw image includes all sectors, even those marked as deleted. This can be useful for forensic recovery, but it also means the image may contain sensitive data you thought you had erased. Use a secure erase tool if you want to remove data permanently.

Can I clone an SD card that has errors?

You can try, but if the card has bad sectors, the imaging tool may hang or fail. Some tools like ddrescue are designed to handle errors by skipping bad sectors and logging them. It is often better to use ddrescue on Linux for a failing card, as it will attempt to read as much as possible.

How long does it take to clone a 32 GB SD card?

It depends on the card’s read speed and your card reader. A typical Class 10 card might read at 20-40 MB/s, so a 32 GB card could take 10-20 minutes. A high-speed UHS-II card with a compatible reader can be faster. The write speed to your hard drive also matters.

Do I need to format the new card before restoring an image?

No. The imaging process overwrites the entire card, including the partition table and file system. Any existing formatting is replaced. In fact, you should not format the new card beforehand, as it is unnecessary and could confuse the tool if it tries to mount the card.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.