Every maker has a version of the same story: a board that worked, a laptop that did not survive, and a design that now exists only as the physical PCB on the bench. PCB projects are unusually painful to lose because they are not one file — they are a small archive of sources, exports and notes, and recreating them means redoing layout work that took evenings, not minutes. This guide sets out a simple, qualitative backup system for those files, built on the well-known 3-2-1 principle and tailored to what a PCB project actually contains.
The 3-2-1 principle, in plain terms
The 3-2-1 rule is a rule of thumb for keeping data safe: keep three copies of anything important, stored on two different kinds of media or locations, with one copy kept off-site — somewhere a single theft, fire or flood at your desk cannot reach. Makers do not need enterprise tooling to follow it. In practice it usually means: the working copy on your computer, a second copy on a separate drive or home storage, and a third copy in cloud storage. Each layer protects against a different failure — accidental deletion, a dead drive, and losing the building, respectively — and the system only works if making the copies is habitual rather than heroic.
What to keep from every PCB project
Back up the project, not just the design file. A complete, restorable PCB project archive contains: the CAD project sources — schematic, board layout and any local libraries or footprints you created, since a layout without its custom library parts may not open cleanly elsewhere; the exported fabrication set exactly as sent to the fab — Gerber layers, the Excellon drill file and, for assembly, the pick-and-place file; the bill of materials and your sourcing notes, including any substitutions you made during the build; and a short build note recording what the board is, which revision it represents, and anything you would tell your future self — a jumper you always fit, a part that ran hot, the bodge you applied to the first batch. That note is the file most people skip and most wish they had.
Version the exports, not just the sources
Sources evolve continuously, but fabs receive snapshots. Keep each released fabrication set in its own clearly named folder alongside the sources at that moment, so the Gerbers on your disk always answer the question: what exactly did the fab build? This discipline pays off the first time a delivered board misbehaves — you can open the precise Gerber set that produced it in Gerbv, using the opening guide, and check the physical board against the exact data it was made from, rather than against a design that has since been edited three times. It also protects you socially: when you share files with a collaborator or a fab’s support desk, everyone inspects the same snapshot.
A folder habit that survives enthusiasm
Backup systems fail socially before they fail technically. Keep the structure boring and identical for every project: one project folder, with sources at the top level and dated release folders beneath it, each holding the Gerbers, drill and assembly files for that revision plus the BOM and build note. Boring is the point — a structure you can reproduce half-asleep after a long build session is one you will actually maintain. Whatever CAD tool you use, from the workflows covered in our KiCad checking guide to the other export guides on this site, the archive shape stays the same.
The cloud copy, and one honest option
The off-site copy is the layer makers most often postpone, because it needs a decision. Any reputable cloud storage you already use satisfies the principle; what matters is that the project archive lands there automatically or by a routine you trust, not that it uses a particular brand. If you are choosing a service for this role, you can look at pCloud — that is an affiliate link, and purchases through it may earn this site a commission at no extra cost to you, as set out on our Affiliate Disclosure page. Judge any cloud option, including that one, by the same plain criteria: does it sync or accept uploads the way you work, can you restore a whole project folder easily, and will you still be using it in three years? A backup you abandon is not a backup.
Test the restore before you need it
A backup that has never been restored is a hope, not a system. Once per project — and at least once while setting your system up — perform a trial restore: copy the archive to a spare folder or a different machine, open the sources, and load the released Gerber set in the viewer from the download page. Confirm the drill file overlays the copper, the BOM opens, and the build note makes sense to you cold. The test takes minutes and catches the classic silent failures: the library that never got copied, the export folder that was empty, the cloud folder that synced everything except the one subdirectory that mattered.
What this system deliberately leaves out
This is a maker’s system, not an IT department’s. It does not prescribe backup software, schedules measured in hours, or retention policies — for design files that change when you work on them, a copy made at every release and at every work session’s end, in three places, is a proportionate defence. If your boards become a business, graduate the system then; the archive structure above scales with you, because the habit — complete project, versioned exports, one off-site copy, tested restores — is the same at every scale. Start it with your current project, before the story at the top of this guide becomes yours.
Frequently asked questions
What does the 3-2-1 backup rule mean for PCB files?
Keep three copies of each project archive, on two different kinds of storage, with one copy off-site — typically your working computer, a separate local drive, and a cloud copy. Each layer guards against a different loss: deletion, drive failure, and losing everything at one location.
Which files belong in a PCB project backup?
The complete project: CAD sources with any custom libraries, the exact Gerber, drill and pick-and-place sets sent to the fab for each revision, the BOM with sourcing notes and substitutions, and a short build note describing the revision and anything future-you needs to know.
Why keep old Gerber exports if I have the design sources?
Because the fab built a snapshot, not your current sources. Keeping each released Gerber set lets you compare a delivered board against the exact data it was made from, reproduce an order precisely, and debug discrepancies without guessing which edits came later.