How to Use Windows File History to Back Up Your Laptop

Why a programmer needs a backup routine

A laptop is a tool; the files on it are the work. For a programmer, those files include source code, editor settings, shell configuration, environment files, notes, and local scripts. A backup routine protects the work, not the hardware.

Windows File History is the built-in way to keep copies of files in your user profile. It watches folders and keeps earlier versions, so you can undo a bad edit or recover a file after an accidental delete. It does not replace version control. Keep using git or your team's system for repositories; File History covers files that version control does not.

What File History covers and what it misses

File History is designed for personal files: Documents, Desktop, Pictures, and other folders in your user profile, plus folders you add. For a developer, that usually means editor settings, shell configuration, notes, and local project folders stored under your user directory.

It does not produce a full system image. Windows, installed programs, and operating system files are outside its scope. If your laptop will not boot, File History alone will not restore Windows. Create a Windows recovery drive as a separate task.

• Project directories that are not pushed to a shared repository
• Dotfiles and shell configuration
• Environment files and local scripts
• Notes, markdown files, and meeting notes
• Local data files you do not want to rebuild by hand

How to set up File History in Windows

Set up takes a few minutes. Connect an external drive with enough free space for your user files and the older versions you want to keep. Open Windows Settings and search for File History, or open the Control Panel and choose File History. Turn it on and select the external drive.

If your code projects live outside the default user folders, add those folders so they are included. Once enabled, File History keeps versions in the background while you work. The exact wording in Settings changes between Windows releases, but the feature is still called File History.

• Connect the backup drive and confirm Windows recognizes it.
• Open Settings and search for File History, or open Control Panel and select File History.
• Choose a drive and pick the external drive.
• Turn on File History.
• Add any folders outside the default user folders.
• Keep the drive connected for continuous backups, or plug it in on a schedule.

Choose the backup drive and the right connection

The external drive connects over USB, and the port matters as much as the drive. Newer laptops often use smaller USB-C ports, while older drives and docks use USB-A. If your laptop only has USB-C, use a USB-C drive or an adapter. See the laptop ports guide and the USB-C vs Thunderbolt guide before buying a dock or drive.

A drive that is at least as large as your internal drive is a practical rule, because File History keeps older versions as well as current files. If your internal drive is nearly full, a backup drive will not solve the underlying storage problem. The storage explainer and the how much laptop storage guide help you decide how much internal room you actually need.

Restore a file from an earlier version

Restoring is the other half of backup. In File History, you can browse past versions of a folder and restore one. This is useful when you overwrite a config file or delete a folder by mistake. Because File History keeps older versions, the restore step can pick a point before the change.

Version control also gives you history, but it is usually limited to one repository. File History covers the rest of your user profile. Keep both running. A full system restore still depends on a recovery drive and your backup drive; see the system restore point guide for another layer.

The laptop specs that make backup painless

File History does not need a fast CPU or a dedicated GPU. It needs storage and a reliable connection. A laptop with a roomy SSD makes it easier to keep code, containers, and virtual machines without swapping drives. A backup drive is then an addition, not a constant juggling act.

If you use Docker Desktop on Windows, Docker's Windows install page is the starting point, and the container and VM specs article covers the heavier side of local development. File History can protect your source folders and configuration; it is not the tool for backing up an entire container image cache or a virtual machine disk.

Visual Studio Code's own requirements page keeps the editor baseline modest, so you can choose a laptop based on your workload rather than on backup software. Intel's processor naming guide explains the H, P, and U suffixes that appear on Windows laptops, which helps you separate high-performance machines from thin-and-light ones. On the GPU side, NVIDIA's RTX 50 Series page describes current GeForce laptop options if local AI or game development is part of your plan.

What to pick for your work

Questions

Is File History a full system backup?

No. File History protects files in the folders you choose, but it does not image Windows or your installed programs. Create a recovery drive separately so you can restore the operating system.

Does File History replace git?

No. Git tracks changes in a repository with commits and branches, which is what you want for collaborative code. File History protects files that are not in a repository, such as shell configuration and local notes.

Can I back up Docker data with File History?

File History is not designed to back up container image caches or virtual machine disks. Use Docker volumes or a separate image export workflow for container data, and let File History cover your source folders and configuration.

What kind of external drive should I use?

Use a drive with at least as much space as the user data you want to protect, because File History keeps older versions. Match the connection to your laptop's port. If your laptop uses USB-C, a USB-C drive avoids adapters.

How often should I plug in the backup drive?

The practical answer is to keep it connected while you work, or connect it on a schedule you can remember. File History runs in the background and stores versions as long as the drive is available.

Will File History use a lot of CPU while I code?

No. File History is designed to copy changed files in the background. Your laptop's CPU choice matters more for compiling, running containers, and machine learning; see the laptop processor guide if you are weighing that trade-off.