Skip to content
RESEARCH-BASED GUIDES. PRACTICAL EVERYDAY ADVICE.How we pick products
RTReviewstookA clearer perspective
Storage

5 Best microSD Cards for Raspberry Pi 4 and 5 (2026)

Best microSD Cards for Raspberry Pi 4 and 5 compared from Amazon listings, with who each pick suits and what to check before buying.

We may earn a commission from qualifying purchases. How we pick products

Where to buy

Check the latest price, availability and delivery on Amazon. Orders are placed on Amazon. We may earn a commission from qualifying purchases.

See 3 more Amazon options
Read the full guide ↓

Disclosure: As an Amazon Associate, reviewstook.com earns from qualifying purchases. Links to Amazon on this page are affiliate links; they cost you nothing extra.

Preloaded cards save setup time; known brands reduce failures.

This guide is built from Amazon product listings and maker specs, not our own testing, so confirm compatibility, speed ratings and current price on each product page.

Check the current price on Amazon before you buy.

Last updated: November 1, 2026.

Concept illustration of microSD cards beside a single-board computer with exposed ports and pins.
AI-generated conceptual illustration; not a photograph of a specific product or a hands-on test.
In this guide

Quick Picks

Product Type Best for
SIX M100 64GB Micro SD (A1, U3, V30) microSD card Raspberry Pi
SanDisk 64GB Ultra microSD microSD card (up to 140MB/s read) Raspberry Pi
64GB microSD with Raspberry Pi OS Preloaded Preloaded microSD Raspberry Pi
Beamo 64GB microSD with Raspberry Pi OS Preloaded microSD Raspberry Pi
SanDisk 32GB Ultra microSDHC (A1) microSDHC card (A1, 120MB/s read) Raspberry Pi

Our Picks

Top pickBest for raspberry Pi

1. SIX M100 64GB Micro SD (A1, U3, V30)

A SIX M100 64GB Micro SD (A1, U3, V30) (microsd card), per the listing. Check price on Amazon.

Good for: Raspberry Pi. Watch out: Lesser-known brand.

Check on Amazon

2. SanDisk 64GB Ultra microSD — 5 best microsd cards for raspberry pi 4 and 5 (2026)

Best for raspberry Pi

2. SanDisk 64GB Ultra microSD

A SanDisk 64GB Ultra microSD (microsd card (up to 140mb/s read)), per the listing. Check price on Amazon.

Good for: Raspberry Pi. Watch out: Basic speeds.

SANDISK 64GB Ultra microSD UHS-I Card
SANDISK 64GB Ultra microSD UHS-I Card

Check on Amazon

3. 64GB microSD with Raspberry Pi OS Preloaded — 5 best microsd cards for raspberry pi 4 and 5 (2026)

Best for raspberry Pi

3. 64GB microSD with Raspberry Pi OS Preloaded

A 64GB microSD with Raspberry Pi OS Preloaded (preloaded microsd), per the listing. Check price on Amazon.

Good for: Raspberry Pi. Watch out: Check OS version.

Fastoe 64GB Raspberry Pi OS Preloaded (Raspbian) MicroSD Card for RPi 5/500
Fastoe 64GB Raspberry Pi OS Preloaded (Raspbian) MicroSD Card for RPi 5/500

Check on Amazon

Best for raspberry Pi

4. Beamo 64GB microSD with Raspberry Pi OS

A Beamo 64GB microSD with Raspberry Pi OS (preloaded microsd), per the listing. Check price on Amazon.

Good for: Raspberry Pi. Watch out: Check OS version.

Check on Amazon

5. SanDisk 32GB Ultra microSDHC (A1) — 5 best microsd cards for raspberry pi 4 and 5 (2026)

Best for raspberry Pi

5. SanDisk 32GB Ultra microSDHC (A1)

A SanDisk 32GB Ultra microSDHC (A1) (microsdhc card (a1, 120mb/s read)), per the listing. Check price on Amazon.

Good for: Raspberry Pi. Watch out: Small capacity.

SanDisk 32GB Ultra® microSDHC 120MB/s A1 Class 10 UHS-I
SanDisk 32GB Ultra® microSDHC 120MB/s A1 Class 10 UHS-I

Check on Amazon

Best Picks by Category

These labels summarize listing data and are not hands-on test results.

  • Top rated: SanDisk 32GB Ultra microSDHC (A1).
  • Most reviewed: SanDisk 64GB Ultra microSD.
  • Best value: SanDisk 32GB Ultra microSDHC (A1).
  • Lowest price: SIX M100 64GB Micro SD (A1, U3, V30).
  • Premium option: 64GB microSD with Raspberry Pi OS Preloaded.

Price, Rating and Review Comparison

Prices change often, so confirm the current price on Amazon.

Product Price Rating Ratings Price tier
SIX M100 64GB Micro SD (A1, U3, V30) Check price on Amazon — — Mid-range
SanDisk 32GB Ultra microSDHC (A1) Check price on Amazon — — Mid-range
SanDisk 64GB Ultra microSD Check price on Amazon — — Mid-range
Beamo 64GB microSD with Raspberry Pi OS Check price on Amazon — — Mid-range
64GB microSD with Raspberry Pi OS Preloaded Check price on Amazon — — Premium

How Much Feedback Backs Each Rating

A high average from a handful of ratings is weaker evidence than a slightly lower average from thousands. Here is how the sample size looks for each pick.

  • SIX M100 64GB Micro SD (A1, U3, V30): a moderate sample size.
  • SanDisk 64GB Ultra microSD: a large sample size.
  • 64GB microSD with Raspberry Pi OS Preloaded: a small sample size, so treat its feedback cautiously.
  • Beamo 64GB microSD with Raspberry Pi OS: a small sample size, so treat its feedback cautiously.
  • SanDisk 32GB Ultra microSDHC (A1): a large sample size.

How to Choose

Capacity

128GB to 256GB covers most uses. Check the maximum your device supports.

Speed rating

U3, V30 and A2 describe sustained video and app performance. Match them to your device.

Seller and fakes

Buy from a reputable seller to avoid counterfeit cards.

Random Access Speed and Why A1 and A2 Matter on a Pi

Many buyers look at the big read-speed number on the front of a card and assume the highest figure gives the best result. For a Raspberry Pi that runs its operating system from the card, that number tells only part of the story. An operating system does a huge amount of small reads and writes in scattered places, such as loading programs, writing logs and updating settings. How a card handles those small random operations often decides how responsive the board feels.

The A1 and A2 marks are application performance classes that describe minimum performance on exactly that kind of small random work. The A1 mark appears on several cards in this guide. A2 is a higher class, but benefits depend on the host supporting the extra command features it relies on, so check the Raspberry Pi documentation for your board before paying more for it. Without that support, an A2 card behaves like a good A1 card.

The U3 and V30 marks, which appear on the SIX M100 listing, describe sustained write speed for video. They are useful if your Pi records video or camera streams, and less central for a desktop or a server that mostly does small tasks.

In practice, look for a recognized A1 or better rating, a maker you can verify, and a capacity that suits your project. Treat any very high claimed speed on a card with no application class as a warning that the listing is aimed at cameras, not single-board computers.

Preloaded Cards Versus Writing the System Yourself

Two cards in this guide arrive with Raspberry Pi OS already on them, while the rest are blank. Which route is best depends on your comfort level and your plans.

A preloaded card saves the step of preparing an image on another computer. That is a real convenience for beginners, for classroom use, and for anyone without a card reader. The trade-offs are practical. The system software on the card might be older than the current release, so check what version the listing names, and plan to run the updates after first boot. You also depend on the seller having prepared the card correctly.

Writing the system yourself takes a few minutes with an imaging tool on a computer. You choose the version, set a hostname, and often set up network access and a user account before first boot. This approach suits anyone who wants a headless setup with no monitor, or who wants a lightweight version for a small project.

Whichever route you take, you will need a way to read cards on your computer unless the preloaded card is all you need. A blank card is cheaper and more flexible, and a preloaded one is easier. If you plan to experiment, buy a second card so that your working setup stays safe.

Capacity Planning for Pi Projects

Capacity needs vary widely. A minimal command-line version of the operating system fits comfortably on a small card, while a full desktop version with a handful of applications needs more room. After the system, think about what your project stores: media libraries, databases, logs, downloaded files, camera recordings or game ROMs.

A common mistake is buying a very large card for a project that writes little. Extra space does not make the board faster, and if the card fails you lose more data in one place. The opposite mistake is choosing the smallest card and running out of space after updates, because the system itself needs working room.

Check the card type your board expects. Cards of 32GB or smaller are labeled SDHC and larger cards are labeled SDXC. Both are normally supported by recent boards, but the documentation for your exact model is the final word. The 32GB and 64GB cards in this guide are enough for many learning projects and home servers, while media centers and recording tasks may call for more.

If your project will hold bulk data, such as a photo archive, keep that on a separate drive or a network share. Putting only the system on the card reduces writes and makes replacement easier.

Power, Safe Shutdown and Card Corruption

Most card problems on single-board computers are not manufacturing faults. They come from power interruptions. If the board loses power while writing, the file system can be left in a broken state, and the board may refuse to boot or show odd behavior. Using a power supply that is suitable for your board model and cable, and avoiding cheap or thin cables, reduces the chance of voltage dips. The board or the operating system may warn you about low voltage, and you should take that seriously.

Shut the system down from the desktop menu or with the shutdown command, wait for the activity light to stop, and only then remove power. Pulling the plug is a common cause of corruption. If your board lives somewhere that loses power often, consider a small battery backup or a power setup with a switch.

Reduce unnecessary writes. Log less, avoid running a swap file on the card where possible, and keep heavy databases or downloads on another drive. Some projects use read-only configurations for kiosks and signs, which helps a lot but takes more setup. Follow the maker’s instructions for those.

When trouble appears, try the card in a computer to see whether it is recognized. If the card is readable, you can often reimage it and restore your files from a backup.

Backups, Spares and Other Boot Options

Every card eventually fails, so a backup plan is part of owning a Pi. Once your setup works well, make a full image of the card on your computer with an imaging or cloning tool, and store it somewhere safe. Keep a record of the packages and settings you added, in case you want to rebuild from scratch. Copy project files to another device or a network location on a schedule.

A spare card, labeled with its purpose, lets you swap quickly. It is also a safe place to test updates or new software before touching your main system.

The post notes that heavily writing projects may do better with an external drive. Recent boards can start from a USB drive or from certain other storage, with a settings change, and the Raspberry Pi documentation explains which options your model supports. Boot from a drive when your project runs a database, constant downloads or heavy logging, and keep a card as a fallback or for simple tasks.

Signs that a card is wearing out include random freezes, files that vanish or become unreadable, slow boots that get worse, and read-only file system errors. Replace the card, restore from your backup, and buy from a seller you trust, since counterfeit cards are a risk on any marketplace.

Preparing a Card for Your First Boot

A Raspberry Pi runs its system software from the microSD card, so preparing it properly sets the tone for everything that follows. The process is simple if you follow the official steps.

  1. Pick the card size you need and make sure it is on the supported list for your Pi model.
  2. Download the official imaging tool from the Raspberry Pi foundation site.
  3. Choose the system software image and the target card, and double-check the drive letter before writing.
  4. Set options like the username, network details and remote access in the tool, if offered.
  5. Write the image, let it verify, and eject the card safely before moving it to the Pi.
  6. Power the board with a supply that meets the official requirements for your model.

Always check the drive you select, since writing an image erases whatever was on that card or drive.

Card Characteristics Worth Comparing

For a Pi, the card does more than store files. It acts as the main disk, so random read and write behavior counts alongside capacity.

Feature Why it matters on a Pi
A1 or A2 class Relates to small random operations, which the system software uses constantly
Capacity Room for the system, updates and your projects
Endurance version Helpful if the Pi logs data or runs around the clock
Brand and seller Reduces the chance of buying a fake card
Adapter or case Handy for moving the card between devices

Corruption can happen if the power is cut while the Pi is writing. Shut the system down from the menu or command line before removing power, and use a stable supply. For projects that must run for months, keep a backup image of the card so you can restore it quickly. Some people also move to external storage for heavy workloads, which is worth considering if the card fills quickly. Keep a label on each card describing what it holds, and handle the contacts only by the edges, as static and dirt can cause read errors.

Backups and Reuse

Once the setup works the way you want, make a copy of the whole card as an image file on your computer. If a card ever fails, you can write that image to a new one and be back in minutes. When you reuse a card for a different project, wipe it with the official imaging tool first so old partitions do not cause confusion. Keep notes on passwords, network settings and installed software somewhere safe, apart from the card itself.

Pick a case that leaves the card slot accessible, because you may swap cards often while you experiment. A simple storage box with numbered slots keeps projects tidy and prevents mix-ups.

Frequently Asked Questions

Does a faster card help?

Only if your device can use the speed.

What is A2?

An app-performance rating useful for apps and games.

How do I spot fakes?

Buy from the official store or a trusted seller and test capacity.

Do I need an A2 card for a Raspberry Pi?

Not necessarily. A2 can help with small random operations, but the board must support the features it relies on. A reputable A1 card is a solid choice for most projects. Check your board's documentation.

How much capacity does a Raspberry Pi need?

It depends on the system version and what you store. A lean command-line setup needs little, while a desktop with applications and media needs more. Put bulk data on a separate drive and use the card for the system.

Why does my Pi not boot after losing power?

A power cut during a write can corrupt the file system. Try the card in another computer, reimage it if needed, and restore your files from a backup. Use a suitable power supply and shut down before unplugging.

Is a preloaded card better for a beginner?

It can be, because it skips image preparation. Check which system version is on the card and run updates after the first boot. Writing your own card gives more control.

Can I run my Pi from a USB drive instead of a card?

Recent boards can usually do so, after a settings change. The Raspberry Pi documentation lists the supported options per model. A drive is worth considering if your project writes a lot.

How can I back up my card?

Create a full image of the card on a computer using an imaging or cloning tool, and store it safely. Also copy project files and a list of installed packages elsewhere.

Will a bigger card make my Pi faster?

No. Capacity does not speed up the board. Random access performance and the application class matter more, so choose a good card in a size that fits your project.

Questions to Ask Before You Buy

A single-board computer relies on its card for almost everything, so choose with care. Consider these questions.

  • What will the board do: media center, home automation, retro games, or learning projects?
  • Will it run all day, or only for short sessions?
  • Do you want a card that already holds system software, or will you write your own?
  • Do you have a card reader and a computer to prepare the card?
  • Does the listing say which board models the card suits?
  • Will you want a second card for experiments, so your main setup stays untouched?

Matching It to Your Use

A small hobby project that logs a few readings is gentle on a card. A system that runs a database, downloads files or writes logs around the clock keeps the card busy. Think about how much your project writes, and plan to copy important files elsewhere on a regular schedule.

Who Should Skip It

If your board can boot from an external drive and your project writes heavily, a drive may suit you better than a card. Beginners who are nervous about preparing images may prefer a card that arrives ready, but check the maker’s listing and instructions for what is included.

Storage and Care Notes

  • Shut the system down properly before removing power or the card.
  • Keep spare cards labeled with their purpose.
  • Make a full copy of a working setup once it behaves the way you want.
  • Store cards in a small case away from moisture and static.

Why the Pi Stresses a Card Like Nothing Else

A Raspberry Pi does not use its card as a shelf; it uses it as its entire hard drive, and it works that drive the way a desktop computer does: constant small reads and writes, logs being appended, caches being churned, databases and services scribbling away day and night. That random-access, always-on pattern is the hardest ordinary life a consumer card can live, harder than photography, harder than video, because it never rests and it never does the card the favour of writing in long, tidy streams. This is why Pi owners learn about card quality the empirical way, and why this guide weights application behaviour and honest manufacture above every headline.

It also explains the Pi community’s folk wisdom: cards die in Pis, Pis corrupt cards, always keep an image. None of that is superstition. It is the predictable result of running a full operating system on a medium designed for cameras, in a machine that can lose power without ceremony. The right response is not fear but system: a good card, a clean shutdown habit, backups of the image, and a spare card ready, which together turn card failure from a disaster into a ten-minute errand.

Reading the Picks for Pi Duty

The SIX M100 leads this guide as a Pi-minded pick, a card whose application behaviour suits an operating system’s chatter. The SanDisk Ultra is the community’s familiar default, the card countless Pis have booted from happily, well suited to ordinary projects and media duties. The preloaded card with Raspberry Pi OS already written is the beginner’s friend, removing the imaging step entirely and getting a first boot in minutes, at the price of trusting someone else’s write of the system. The Beamo preloaded card serves the same first-boot purpose with its own bundle. The smaller SanDisk Ultra closes the list as the spare-and-experiment card, the one to keep imaged and ready, or to sacrifice to a risky project without regret.

Choose by project, not by habit. A Pi running a light, read-mostly duty, a dashboard, a sensor display, a retro games console, asks little and forgives much. A Pi running a home server, a network service, a database or anything that writes logs and state all day asks everything, and deserves the strongest card you can justify plus the backup discipline below. A classroom or a child’s first Pi deserves the preloaded card and a spare, because the lesson should be computing, not imaging.

Imaging, First Boot and the Clean Start

Whether you image a card yourself or buy one preloaded, the first boot deserves care. Use a trustworthy power supply, because more Pi storage mysteries are born of weak power than of weak cards: a Pi that browns out mid-write corrupts cards with an innocent face. Let the first boot complete its setup without interruption, change the default credentials, update the system, and then, before you build anything precious on it, take an image of the working card. That golden image is the foundation of every recovery you will ever do.

Keep the imaging tools and the golden image together, on the computer you would use in a recovery, and label the card with the project and the date it entered service. Pis multiply in a household, cards migrate between them, and six months later nobody remembers which card holds the print server. Labels are the difference between a fleet and a mystery box.

Power, Shutdowns and Corruption Discipline

The single kindest thing you can do for a Pi’s card is to shut the Pi down properly, every time, and to feed it power that does not sag. Pulling the plug on a running Pi is sometimes unavoidable, in a freeze or a failure, but as a habit it is card cruelty, because the system may be mid-write to exactly the structures it needs to boot. Where a Pi runs headless and unattended, consider what happens in a power cut: a small uninterruptible supply, or at least a filesystem and a workload chosen to tolerate interruption, and an image backup that makes the worst case boring.

Heat is the second discipline. A Pi working hard in a closed case cooks its card slowly, and Pis in lofts, garages and greenhouses live at temperatures their owners forget to imagine. Ventilate the case, check the machine’s reported temperature occasionally, and remember that a card in a hot Pi ages faster than the same card in a camera. Retire cards from hot, busy Pis on a schedule rather than on a failure, and demote them to gentle duties clearly labelled.

Backups, Clones and the Spare Card System

A Pi backup is an image, not a folder of files, because what you need on the bad day is the whole working system. Image the card when the project reaches a state you would mourn, after big changes, and before experiments. Keep images dated and keep more than one generation, because the latest image faithfully preserves the latest mistake. Test a restore once, onto the spare card, so that recovery is a procedure you have performed rather than a theory you believe.

The spare card should be a real pick from this guide, imaged or ready to image, stored with the Pi’s power supply and cables. When the working card fails, and in a busy Pi the question is when rather than if, the swap takes minutes and the project survives with its dignity intact. Households and classrooms that run several Pis should standardise card sizes where they can, so one spare and one imaging routine serve the whole fleet.

When to Leave the Card Altogether

Honesty requires the other path: some Pi projects outgrow cards. A busy server writing constantly, a project needing real database behaviour, or a Pi that must run for years untouched may be better served by booting from a USB drive or solid-state storage, which the Pi supports and which tolerates the workload with far less drama. The card then becomes the bootstrap or the backup rather than the battlefield. Recognising that moment is not disloyalty to this guide; it is the guide’s own logic, matching the medium to the work, applied one level up.

For the great majority of Pi projects, though, the card remains the right answer: cheap, silent, tiny and, with the disciplines above, dependable enough. The picks here, a good power supply and an image backup are a complete system. Most Pi card horror stories, examined closely, are missing one of those three legs, and the fix is rarely a more exotic card; it is the missing leg, supplied at last.

More Questions Worth Asking

How can I tell if my Pi’s problem is the card or the power supply?

Suspect power first if the Pi reboots, freezes under load or corrupts repeatedly across different cards; suspect the card first if one card misbehaves in this Pi and in a computer while other cards behave in both. The cross-check takes minutes: known-good supply, known-good card, one change at a time. Pi troubleshooting rewards that patience more than any other skill, because the two great causes wear each other’s coats.

Can I move a card from an older Pi to a newer one?

Often yes for the same system image, provided the newer machine supports it and the system is updated, but expect the first boot to be slower and check that everything you rely on still runs. For a card carrying a precious project, image it first, test the move on the copy, and keep the original untouched until the new home has proven itself over days, not minutes.

What size card does a Pi really need?

Enough for the system, the project and comfortable working room, with the same reserve discipline as any drive: systems that run nearly full misbehave in ways that look like card faults. Light projects live happily in the smaller picks here; media centres, servers and anything collecting data should take the larger end and the headroom it buys. Bigger is not faster for a Pi, but roomier is calmer.

Projects That Teach Card Discipline

Some Pi projects are gentle teachers and some are strict ones. A retro games console barely writes, forgives everything, and is the perfect first project for learning imaging and backup without tears. A media centre writes in bursts and teaches capacity planning. A home server, a weather station with a database, or a network monitor writes constantly and teaches the full curriculum: power discipline, heat, imaging, scheduled replacement. Choose your first project for the lessons you want, and let the card habits grow with the workload rather than arriving all at once with the hardest project you own.

Classrooms and clubs running many Pis should standardise ruthlessly: one card type, one image, one labelling scheme, one spare per few machines. Standardisation is what makes a fleet teachable, because every problem appears in a known environment and every fix can be shared. The picks in this guide suit that fleet logic well, with the preloaded cards removing the imaging bottleneck at the start of term and the established cards carrying the machines that graduate to real duties.

Reading the Signs: A Pi Card Health Routine

Give a working Pi a monthly minute. Check the machine’s temperature and uptime, glance at free space, and confirm your latest backup image is where you think it is. Every few months, or before any big change, take a fresh image. Watch for the early mumbling of a tiring card: odd slowness, a service that fails to start once and then behaves, a boot that needed a second attempt. Each is cheap to investigate at the monthly minute and expensive to meet unprepared at midnight.

Keep a written line per Pi: project, card, start date, last image date. Four facts, kept current, are the entire management system a household fleet needs, and they fit on an index card taped inside the project box. When a card finally fails, that card, the index kind, tells you what was lost, which is usually nothing, because the image from last month is already waiting.

Disposing of dead cards properly

A Pi card can hold passwords, keys and a household’s whole network configuration, so a dead card is not ordinary rubbish. Wipe what can be wiped, and physically destroy cards that held anything sensitive rather than binning them intact. The same care applies to cards you pass on: a fresh image for a friend is a kindness, while your old system image with your credentials still on it is a liability wearing a favour’s clothes.

Headless Pis, Remote Pis and Cards You Cannot Reach

The hardest Pi to forgive is the one you cannot touch: the sensor Pi in the attic, the camera Pi in the garden, the relative’s Pi in another town that you maintain by phone. Remote Pis raise every stake in this guide. Their cards must be the strongest picks, their power the cleanest, their images the most current, because a card failure there is not a ten-minute swap but a journey, a ladder or a parcel. Before deploying a Pi beyond arm’s reach, burn in its card at home through days of its real workload, take the golden image, and write the recovery instructions for the person nearest to it, in words that assume no expertise at all.

Give remote Pis a way to be helped: a labelled spare card posted with the instructions, a household member who knows which end of the machine the card lives in, and update habits that never leave the machine mid-change when nobody can rescue it. Many remote Pi failures are not failures of hardware but of distance, and distance is a design constraint to be planned for, exactly like heat or power.

Retro Games, Media Centres and the Joyful Pis

Not every Pi is a server, and the joyful ones deserve their own word. A retro games machine asks its card for libraries and saves, read far more than written, and rewards capacity and a good backup of the save files above all else. A media centre asks for bursts of writing as libraries update and for calm behaviour across years of evenings. Both are gentle compared with a server, and both are ruined by the same thing: the lost save, the corrupted library, discovered at the start of a free evening. The image backup is the whole secret, taken when the machine is perfect, kept where the household keeps its other digital valuables.

Joyful Pis also make the best teaching machines for everything in this guide, because their failures are painless. Practise imaging, restoring and swapping cards on the games machine, and the skills will be there, calm and ready, on the day the serious Pi needs them at midnight.

Community Wisdom, Examined Kindly

The Pi community trades card advice with great confidence and variable accuracy, and a new owner benefits from knowing which sayings to keep. Keep the ones about power supplies, clean shutdowns and backups; they are earned. Treat with caution any claim that one particular card is magically immune to Pi life, or that a card once corrupted is a card brand condemned forever; both confuse a system property with a product property. And ignore entirely the advice to keep reusing a card that has corrupted twice on the theory that the third format will charm it. In Pi service, a card’s second corruption is its resignation letter.

The deeper truth the community knows, beneath the folklore, is that Pi storage is a system with four parts: the card, the power, the habits and the image backup. Attend to all four and almost any pick in this guide will serve you well. Neglect any one and the finest card ever made will eventually star in a forum post. Choose your card, then go and build the other three legs, and your Pi will repay you with the rarest thing in hobby computing: a machine that is simply there, working, every time you reach for it.

Begin wherever your Pi is today. If it has no current image, take one this week, before the next experiment, the next update, the next power cut. If its card is an unknown from a drawer, plan its honourable replacement with a pick from this guide at the next natural pause. If its power supply is the one that came free with something else, let that be the next small purchase after the card. Each step is minutes, and together they convert a fragile project into a household appliance in the best sense: present, useful and unregarded.

The Pi was designed to make computing cheap, small and everywhere, and its card is the price of that miracle: a consumable heart that asks for a little system in return. Pay that small price gladly, in labels, images and spares, and the miracle runs for years.

Consider the Pi that runs for five years in a cupboard, serving a household without a single dramatic day, because its owner spent one evening on power, card and backups at the start. Nothing about that story is exciting, and it is the best story a Pi can have. The projects that fill forums are the ones missing a leg of the system; the projects that fill homes with quiet usefulness are the ones standing on all four. Let yours be the second kind, and let its card, whichever pick from this guide it is, grow old in service rather than young in a drawer of might-have-beens.

Write the index card. Take the image. Label the spare. Three acts of ten minutes each, performed once, are the entire difference between a Pi that is a project and a Pi that is a possession.

And if you are buying for a first Pi, buy the card and the spare together, and image the spare the same evening the machine first boots perfectly. That single evening’s work is the seed from which years of calm computing grow, and it is the cheapest insurance in the whole of this hobby. The machine will teach you everything else it knows at its own pace; the card system is the one lesson to learn before the first lesson is needed.

Do the three acts before the next project lands on the bench. Future you, reaching for the Pi at midnight a year from now, will find a machine that starts, a card that holds, and an image that restores, and will never know how close the alternative history came. That ignorance is the reward, and it is earned entirely in advance, in ten-minute instalments, starting now.

Finally, teach the system to the next person who touches the machine: where the image lives, which card is the spare, why the plug is never pulled. A Pi understood by two people is twice as immortal as a Pi understood by one, and the teaching takes less time than the recovery it prevents.

Begin with the image you take tonight. Every calm year that Pi ever gives you will be traced back, if anyone bothers to trace it, to the evening somebody decided the system mattered more than the shortcut. Be that somebody, once, and the machine does the rest.

Card, power, habits, image: four legs, one table, years of evenings at which nothing whatsoever goes wrong. That uneventful table is the finest furniture in hobby computing, and it is built from the contents of this guide and one free evening.

Start tonight, with the Pi humming beside you and the imager open. The first backup is the hardest only because it is first.

It takes one evening, once, and the machine remembers it for years afterwards.

Begin there, and begin now, while the machine is healthy.

Bottom Line

Pick a known-brand A1 card, or a preloaded card to skip setup.

More Storage Guides