Verdict up front: buy a kit built around the board you actually want, with an official-style power supply matched to that board, a case with decent airflow, and an endurance or reputable standard microSD card of at least 32 GB. If a kit is much cheaper than the alternatives, check the power supply first — that is usually where the saving came from, and it is the part most likely to corrupt your card.

Win32 Disk Imager is Windows-only, version 1.0.0 from 2017-03-08. You will use it on your Windows PC to write the Pi image to the card, then move the card to the Pi. The flashing steps are covered in flashing Raspberry Pi OS with Win32 Disk Imager and in how to use Win32 Disk Imager.

What a good starter kit must contain

• The board: choose the Pi model for your project, not the cheapest board in the listing. Check that the kit listing names the exact model, memory size, and board revision, and that it matches what you intend to run.
• An official-style power supply: this is the non-negotiable item. An underpowered supply corrupts cards, causes brownouts under load, and produces boot failures that look like bad images. The supply must be rated for your specific Pi model, with the right connector, and it should come from the kit maker or a reputable brand, not an unlabelled generic charger.
• A case with airflow: a sealed plastic box traps heat and throttles the Pi under sustained load. Look for ventilation slots or a fan mount, and easy access to the microSD slot so you can swap cards without dismantling the case.
• A microSD card you can trust: at least 32 GB, from a reputable brand, with A1 or A2 class and U3 and V30 markings. For an always-on Pi, an endurance card is the better choice. Our card guides cover standard Pi cards and endurance cards in detail.
• A card reader for your PC: you need a way to write the image from Windows. A USB 3.0 reader is covered in our card reader guide, and it is worth having even if the kit includes one, because kit readers are often the weakest part.
• Cables you will actually use: a suitable video cable for your display and, if you plan wired networking, an Ethernet cable. Check the Pi model’s video connector before assuming an old cable fits.

Comparison: kit types

For current kits and cards to start from, see this Raspberry Pi starter kit on Amazon (Sponsored) and this microSD card for Raspberry Pi on Amazon (Sponsored) — check the current price and confirm the board model, power supply rating, and card capacity and class markings on the product pages. See our affiliate disclosure for how sponsored links work on this site.

What to avoid

• An unlabelled power supply: if the listing does not name the supply rating or brand, assume it is undersized. This is the single most common kit failure.
• A no-name card bundled in the kit: test any bundled card before you trust it. See testing a card with h2testw if you suspect the capacity is not real.
• A case that blocks the card slot: you will swap cards often while learning. A case that forces full disassembly for every swap gets old fast.
• Flashing to the wrong drive: Win32 Disk Imager Write overwrites the entire destination drive. Double-check the drive letter every time, especially when a kit reader adds a new drive letter you did not expect.

Before you flash: a checklist

Unpack and inspect the supply rating, test the card, and confirm you have a USB reader and a Windows PC with Win32 Disk Imager installed from our download page. Flash the image, verify it, insert the card into the Pi, connect the official-style supply last, and watch the first boot. If the Pi will not boot, work through Raspberry Pi will not boot after flashing before assuming the board is faulty — in a new kit, the supply and the card are the likelier culprits.

Frequently asked questions

Do I need the official Raspberry Pi power supply?

You need a supply matched to your Pi model that can deliver stable power under load, and an official-style supply is the safest way to get that. An underpowered or unstable supply is a common cause of card corruption, random reboots, and failed flashes, so do not reuse an old phone charger and hope for the best.

Can I flash the card before the kit arrives?

You can prepare the card image on your Windows PC with Win32 Disk Imager before the board arrives, but do not judge the result until you boot it in the Pi with a proper power supply. A card that seems fine on a PC can still fail to boot on an underpowered Pi.

What size card should a starter kit include?

A 32 GB card is enough for a basic Raspberry Pi OS install, and 64 GB gives comfortable room for updates and projects. For a Pi that will run all day, choose an endurance card instead of a standard card.

Verdict up front: buy a drive sized for a library of full-size images, not for a single backup. A 1 TB external drive is a sensible minimum for a handful of cards, and a 2 TB drive is the safer default if you keep several 64 GB or 128 GB card images. A portable hard drive is the best value for a deep archive; an external SSD is the better choice if you restore often or carry the drive with you.

The core fact is this: Win32 Disk Imager Read output size equals the full device size, with no compression. A 128 GB card makes a 128 GB .img file, even if only a few gigabytes of that card hold actual files. A 64 GB card makes a 64 GB file, and a 32 GB card makes a 32 GB file. Back up five 128 GB cards and you already need 640 GB, before a single other file. That maths, not marketing, should set your drive size.

Capacity maths: size for the library

Compression changes the picture after the fact. Our guide to compressing an .img file with 7-Zip shows how empty space in an image often compresses well, but you should not buy a drive that only fits if every image compresses perfectly. Buy for the uncompressed total, then treat compression as a bonus. The backup workflow itself is covered in backing up an SD card to an .img file, and restoring is covered in restoring an .img backup to an SD card.

Comparison: hard drive versus SSD for .img archives

For a current drive to start from, see this backup drive on Amazon (Sponsored) — check the current price and confirm the capacity, connector, and whether it is a hard drive or an SSD on the product page. See our affiliate disclosure for how sponsored links work on this site.

What to avoid

• Buying exactly one image worth of space: the second backup is when the drive runs out. Add room for at least twice the cards you have today.
• Keeping the only copy on the same card or PC you imaged: a backup on the device it backs up is not a backup. Keep images on a separate drive, and ideally a second copy elsewhere.
• Deleting the original card before verifying the image: verify the image, or at least confirm its size matches the full card size, before you wipe or reuse the source card.
• Forgetting that Write overwrites everything: Win32 Disk Imager Write overwrites the entire destination drive. Restoring an image to the wrong drive destroys whatever was on it, so always check the drive letter first.

A simple archive routine

Name each image with the card, the date, and the project, for example pi-media-2026-10-24.img, and keep a short text note alongside it listing what the image contains. Store images on the backup drive, compress older ones you rarely need, and keep one copy offsite if the images matter — cloud backup for .img files is compared in our pCloud versus Backblaze guide. You can get Win32 Disk Imager from our download page.

Frequently asked questions

How much backup drive space do I need for .img archives?

Size it for a library, not one image. Because Win32 Disk Imager Read output equals the full device size with no compression, a 128 GB card makes a 128 GB .img file, so ten such backups need over a terabyte before you add any other files.

Can I compress .img files to save space?

Yes, after the image is created you can compress it with a tool such as 7-Zip, which often shrinks an image a lot when much of the card is empty. Keep at least one uncompressed copy of any image you may need to restore in a hurry, and see our compression guide for the steps.

Should I use an SSD or a hard drive for .img archives?

A hard drive usually gives more capacity per unit of money, which suits a large archive library. An SSD is faster and tougher when you carry it around, but you pay more per gigabyte, so it is best for a working set rather than a deep archive.

Verdict up front: buy a USB 3.0 reader with UHS-I support, from a reputable brand, with the connector your computer actually has. USB-C readers suit modern laptops, USB-A readers suit older desktops, and a reader with both connectors covers both. Avoid no-name USB 2.0 readers for anything larger than a small test image.

Win32 Disk Imager is Windows-only, version 1.0.0 from 2017-03-08, and it writes the whole image to the destination drive. A slow reader does not change what gets written, but it stretches the job out and increases the chance of an interruption. The flashing steps are covered in how to use Win32 Disk Imager, and Pi-specific flashing in flashing Raspberry Pi OS.

What actually matters in a reader

• USB 3.0 versus USB 2.0: this is the single biggest difference. USB 2.0 limits transfers to a level far below a modern card’s capability, so a large image flash can take several times longer. USB 3.0, on a USB 3.0 port, removes that ceiling.
• UHS support: UHS-I is the standard for almost all Pi cards. The reader must support the card’s bus mode to reach the card’s speed; a reader that only supports older modes will hold a fast card back.
• USB-C versus USB-A: match the reader to your computer’s ports. A USB-C reader on a laptop with only USB-C ports avoids dongles, while a USB-A reader is simpler on an older desktop. Dual-connector readers are a good compromise if you use both.
• Slot types: a microSD slot is essential for Pi cards. A full-size SD slot as well is handy if you also flash camera cards, but do not pay for slots you will never use.
• Build and cable: a reader that disconnects when bumped will corrupt a flash. A short, solid cable or a direct plug-in design is more reliable than a long, loose one.

Comparison: reader types

For a current reader to start from, see this USB SD card reader on Amazon (Sponsored) — check the current price and confirm USB 3.0 support, UHS-I support, and the connector type on the product page. See our affiliate disclosure for how sponsored links work on this site.

What to avoid

• Using a USB 2.0 port with a USB 3.0 reader: the port, not the reader, becomes the bottleneck. Plug into a blue USB 3.0 port where one is available.
• Flashing through a cheap hub: unpowered hubs can drop the connection mid-write. Plug the reader directly into the computer for important flashes.
• Ignoring repeated failures: if flashes fail at the same point, try a different reader before assuming the card is dead. Slow-write troubleshooting is covered in Win32 Disk Imager slow write speed.
• Forgetting the destination check: Win32 Disk Imager Write overwrites the entire destination drive. Always confirm the drive letter, and read wrong-drive overwrite recovery before you need it, not after.

A note on verifying after flashing

A good reader also makes verification practical. Win32 Disk Imager can verify an image after writing, and verification is worth the extra minutes when the card will go into a Pi you cannot easily reach. If verification fails, try the reader on another port, then another reader, then test the card itself with h2testw. You can get Win32 Disk Imager from our download page.

Frequently asked questions

Does a USB 3.0 reader really flash faster than a USB 2.0 reader?

Yes, in practice. USB 2.0 caps the whole transfer at a level well below what a good card can sustain, so flashing a large image takes noticeably longer. A USB 3.0 reader on a USB 3.0 port removes that bottleneck, although the card itself is still the final limit.

Do I need a reader that supports UHS-II?

Only if your cards are UHS-II cards and you need their extra speed. Most Raspberry Pi cards are UHS-I, and a good UHS-I USB 3.0 reader is enough for flashing them. Paying for UHS-II support you will never use does not speed up a UHS-I card.

Can a cheap reader damage a card?

A poor-quality reader is more likely to cause failed writes, disconnects, or corrupted images than physical damage. If flashes repeatedly fail on one reader but succeed on another, replace the reader before blaming the card.

Verdict up front: for an always-on Pi, buy a card from a named endurance line, such as the Samsung PRO Endurance line or the SanDisk Max Endurance line, in at least 32 GB and preferably 64 GB or larger. The endurance line matters more than the headline speed number, and a larger endurance card generally gives the controller more room to spread writes.

Win32 Disk Imager is Windows-only, version 1.0.0 from 2017-03-08, and its Read output is the full size of the device, with no compression. That matters for always-on Pis too: a backup image of a 64 GB card is a 64 GB file, so plan backup storage accordingly. The flashing workflow is covered in flashing Raspberry Pi OS with Win32 Disk Imager.

Why standard cards fail in always-on Pis

Flash memory wears out with writes. A standard card is designed for intermittent use: a camera writes a batch of photos, then rests. An always-on Pi does the opposite, writing logs, databases, or video segments continuously. Over months, that difference adds up, and the first symptom is often filesystem corruption, read errors, or a Pi that stops booting for no obvious reason.

Endurance lines address this by using flash and firmware tuned for continuous writing. This guide does not quote endurance ratings in terabytes or warranty years for named products, because those figures vary by capacity and by the manufacturer’s current specification sheet. Instead, compare product lines on the product page: look for the endurance designation, the capacity, and the intended use, such as surveillance or dashcam, and confirm the details there before you buy.

Comparison: endurance line versus standard line

For a current endurance line to start from, see this endurance microSD card on Amazon (Sponsored) — check the current price and confirm the endurance designation and capacity on the product page. See our affiliate disclosure for how sponsored links work on this site.

Sizing and setup tips for an always-on Pi

• Size up when you can: a larger card gives the controller more spare area to manage writes. For a recorder or logger, 64 GB is a sensible floor and 128 GB is worth considering.
• Reduce unnecessary writes: send logs to a remote server or a USB drive where practical, and avoid writing large temporary files to the card on every cycle.
• Keep a backup image: image the card while it is healthy. Our guide to backing up an SD card to an .img file shows the process, and restoring an .img backup to an SD card covers getting back up and running after a failure.
• Use a good power supply: brownouts corrupt cards faster than almost anything else. An official-style supply matched to your Pi model is cheap insurance.
• Test before deployment: a card that passes a full write test before it goes into service is far less likely to surprise you later. See testing a card with h2testw.

What to avoid

• Reusing an old phone card for a 24/7 recorder: a card that already served years in a phone has used up much of its write life before the Pi ever sees it.
• Choosing purely on speed class: a fast standard card is still a standard card. For continuous writing, the endurance designation is the deciding factor.
• Running with no backup: every card fails eventually. If the Pi holds data you cannot recreate, schedule regular image backups to a separate drive.
• Ignoring boot failures: if an always-on Pi stops booting, work through Raspberry Pi will not boot after flashing before assuming the board itself has failed.

You can find Win32 Disk Imager itself on our download page. For a Pi that is only used occasionally, the standard-card guidance in our best microSD card for Raspberry Pi guide is the better starting point.

Frequently asked questions

What makes an endurance card different from a standard card?

Endurance lines are designed for continuous writing, such as security cameras and always-on recorders. They are built to tolerate far more write cycles than standard cards, which is why they are the right choice for a Pi that writes logs, recordings, or sensor data around the clock.

Do I need an endurance card for a Pi I only use occasionally?

No. If the Pi runs for a few hours at a time and mostly reads data, a standard card with a good A-class rating is fine. Endurance cards pay off when the Pi writes continuously or runs 24 hours a day.

How long will an endurance card last?

That depends on how much data the Pi writes every day, the card capacity, and the workload. Larger capacities spread writes over more storage, which generally helps longevity, but no card lasts forever, so keep backups of anything important.

Verdict up front: buy a reputable-brand card in the 32 GB to 64 GB range, with A1 or A2 application performance class and U3 and V30 speed classes, from a seller you trust. If the Pi will run all day, every day, read the endurance guide instead and choose an endurance line. For a general-purpose Pi, the class and the seller matter more than chasing the largest capacity.

Win32 Disk Imager is a Windows-only tool, version 1.0.0 from 2017-03-08, and it writes a complete disk image to the card. That means the image must fit on the card, and the card should be tested before you trust it with a project. Our flashing walkthrough is covered in how to flash Raspberry Pi OS with Win32 Disk Imager, and the general workflow is explained in how to use Win32 Disk Imager.

What actually matters when you choose a card

Card marketing leans heavily on one headline sequential speed number. For a Pi, that number is not the whole story. The operating system constantly reads and writes many small files, so random performance and sustained write behaviour matter at least as much as a peak sequential figure printed on the packaging.

• Application performance class (A1 or A2): these classes describe minimum random read and write performance for running apps from the card. They are a useful filter, but they are spec classes, not a guarantee of how a particular card behaves in your Pi.
• Video and bus speed classes (V30 and U3): V30 and U3 indicate a minimum sustained sequential write level. They help with large writes, such as flashing an image or recording video, but they do not by themselves tell you how the card handles small operating-system writes.
• Capacity: a larger card does not make a Pi faster. It gives you more room for files, logs, and future updates. A 32 GB card is enough for a basic desktop install; 64 GB is a safer default if you will install extra software or keep backups on the Pi.
• Endurance line versus standard line: standard cards are designed for cameras and phones with intermittent writes. Endurance lines are built for continuous writing, such as dashcams and always-on recorders, and they are the better choice for a Pi that never sleeps. See our endurance comparison for that case.
• Fake-card risk: counterfeit cards report a larger capacity than they really have, then silently corrupt data once the real capacity is exceeded. Buy from a reputable retailer, keep the packaging, and test a new card before you rely on it.

Comparison: which class of card fits which Pi use

For a current product line to start from, see this microSD card for Raspberry Pi on Amazon (Sponsored) — check the current price and confirm the capacity, A-class, and U3 and V30 markings on the product page before you buy. See our affiliate disclosure for how sponsored links work on this site.

What to avoid

• Unbranded or suspiciously cheap cards: if the price is far below every reputable brand for the same capacity, assume the capacity or the speed rating is not real.
• Buying from marketplace sellers with no track record: counterfeit cards are common in third-party listings. Prefer the brand store or a well-known retailer.
• Skipping the test: before you flash anything important, test a new card. Our guide to testing a card with h2testw shows how to spot a fake before it eats your data.
• Using a worn-out old card for a new project: if a card has already shown read errors or failed writes, retire it. A Pi that will not boot after flashing is often a card problem, covered in Raspberry Pi will not boot after flashing.

Before you flash

Once you have a card you trust, flash it with the correct image and verify the result. Win32 Disk Imager can verify an image after writing, and you can find the download on our download page. After a successful flash, if the Pi boots but the filesystem looks small, the fix is usually to expand it, as explained in expanding the filesystem after flashing. Keep a backup image of a working card, because reflashing from a known-good image is far faster than rebuilding a Pi from scratch.

Frequently asked questions

What size microSD card should I buy for Raspberry Pi OS?

For most Raspberry Pi OS installs, a 32 GB card is a comfortable minimum and a 64 GB card gives room for updates, extra software, and a few projects. Larger cards are only needed if you plan to store a media library or many large files on the Pi itself.

Is an A2 card always faster than an A1 card on a Raspberry Pi?

Not necessarily. A2 is a higher application-performance class on paper, but real speed on a Pi depends on the card reader, the Pi model, and random read and write performance, not just the printed class. Check independent reviews and the product page for the class markings rather than assuming the label alone guarantees speed.

Can I reuse a card I flashed with Win32 Disk Imager?

Yes. Flashing overwrites the card, but you can reflash it with a different image later. Just double-check the destination drive letter before every Write, because Write overwrites the entire destination drive.