File History is Windows 11’s continuous backup feature — it monitors your personal folders and automatically copies changed files to an external drive at regular intervals. The key advantage over manual backups: it keeps multiple versions of each file. Overwrite a document with the wrong content, delete a photo by mistake, or need to see what a file looked like three days ago — File History provides the versioned recovery that a single backup point doesn’t. This fits into the wider topic we cover in our Windows 11 How-To Guides.
Quick check: is File History already running on your machine? Settings → System → Storage → Backup → “Add a drive” or shows current backup drive status. Many Windows 11 users have it configured without actively managing it; others have never set it up.
Setting up File History
File History requires an external drive (USB HDD, external SSD, or network location) separate from the drive being backed up. The drive stays connected during backup sessions; if it’s removed, File History simply pauses until it’s reconnected.
Enable via Settings: Settings → System → Storage → Backup → “Add a drive” → select the external drive. File History starts running immediately. The first run copies everything — on a large library, this takes hours. Subsequent runs are incremental, copying only what’s changed since the last backup.
Enable via Control Panel (more options): Control Panel → File History → “Turn on.” The Control Panel interface also shows backup progress, lets you immediately run a backup, and provides the “Restore personal files” option.
What gets backed up
By default: Documents, Music, Pictures, Videos, Desktop, Contacts, and the desktop. The default doesn’t include: Downloads (intentionally, as it fills quickly with files that don’t need versioned backup), AppData (application settings — added manually if needed), or files on other drives (only the system drive’s user profile folders are included by default).
Add folders: Control Panel → File History → “Select folders” → add any folder path. This is how you include project folders outside the default user profile, data stored on a secondary drive, or specific application data folders worth protecting. Each added folder becomes part of the continuous monitoring and backup cycle.
Exclude folders: File History → Advanced settings → “Exclude folders” → add specific folders to skip. Useful for excluding large folders of easily-recreatable content (build outputs, node_modules, temp folders) from the backup to save space on the backup drive.
Backup frequency and retention
Control Panel → File History → Advanced settings → two key settings:
- Save copies of files: how often File History checks for changes and copies them. Default: every hour. Range: 10 minutes to daily. Hourly is reasonable for most users; every 10 minutes for documents that change frequently during active work sessions.
- Keep saved versions: how long to retain older versions before they’re deleted to free space. Default: forever (until the drive fills). Options: from 1 month to 2 years, or forever. Setting a retention limit of 3-6 months prevents the backup drive from filling up while keeping reasonable history depth.
“Clean up versions” button: manually triggers deletion of versions older than the configured retention period. Useful when the backup drive is getting full and you want to free space without waiting for the automatic cleanup cycle.
Restoring files
Two restoration paths:
From File Explorer: navigate to the file or folder you want to restore → right-click → “Restore previous versions” → a list of versions with dates appears → select any version → “Restore” (to the original location, replacing current) or “Restore To” (to a different location, keeping the current version). This is the fastest path for restoring specific files.
From File History interface: Control Panel → File History → “Restore personal files” → a visual timeline shows folder content at different points in time. Use the arrows at the bottom to move through time. Navigate to the folder containing the file you want → click the green restore button. This view is useful for browsing what existed at a specific point in time across entire folders.
Our guide on Windows 11 backup strategies covers File History alongside other backup methods including system images and cloud backup, and our guide on Windows 11 storage management covers managing the backup drive space when File History accumulates large amounts of history. For File History’s technical implementation and the Shadow Copy service it uses, Microsoft’s File History documentation covers the backup architecture and recovery procedures.
File History on a network drive
File History can back up to a network location rather than a directly connected drive. Control Panel → File History → “Select drive” → “Add network location” → enter the network path (servernamesharename or a UNC path). This is useful for households with a NAS device or a shared computer acting as a backup server — everyone’s File History backs up to the central NAS rather than each person needing their own external drive.
Network backup has one important limitation: if the network location is unavailable (the NAS is off, the network connection drops), File History pauses and doesn’t back up until the connection is restored. For continuous backup of actively-changing files: a direct-connected drive is more reliable than network storage that might be temporarily inaccessible.
File History vs OneDrive backup — differences that matter
Both protect files against loss, but they work differently:
| Aspect | File History | OneDrive backup |
| Storage location | External drive (local) | Cloud (Microsoft servers) |
| Version history depth | Configurable (months to forever) | 30 days |
| Accidental deletion recovery | Yes (previous versions retained) | Yes (30-day Recycle Bin) |
| Works without internet | Yes | No |
| Off-site protection | No (unless drive is off-site) | Yes |
| Storage cost | Cost of external drive only | Free 5GB / subscription for more |
Running both simultaneously: File History provides local rapid recovery with deep version history; OneDrive provides off-site protection against fire, theft, or the external drive failing at the same time as the PC. Together they implement the “2” part of the 3-2-1 backup rule (two copies on different media) with OneDrive as the “1” off-site copy.
Troubleshooting File History issues
- File History stopped working: check the backup drive is connected and has sufficient space. File History pauses automatically when the drive is full or disconnected. Control Panel → File History shows the current status and any error messages.
- Backup drive fills too quickly: reduce retention period, add folder exclusions for large/unimportant folders, or use a larger backup drive. Check which folders are consuming the most backup space: navigate to the backup drive → FileHistory folder → shows per-computer, per-user backup folders with sizes.
- Previous versions not showing: ensure File History was enabled and had time to run at least once before the file was lost. Right-click → “Restore previous versions” shows nothing if File History never ran, or if the file was created and deleted in the same interval between backups.
File History is particularly valuable for document workers who edit files repeatedly over time — the ability to compare today’s version with what a document looked like a week ago, or recover a section accidentally deleted three saves ago, addresses scenarios that neither manual backups nor cloud sync handle well. Setting it up properly once, with appropriate frequency and retention settings, provides continuous protection that runs silently and invisibly until it’s needed.
File History and system performance
File History’s backup process runs at low priority — it doesn’t visibly impact system performance for most users. During the initial full backup (which can take hours for large libraries): disk activity will be elevated. Subsequent incremental backups are much lighter, typically running in under a minute when changes are modest.
On machines with HDDs rather than SSDs: File History’s disk activity during backup can occasionally cause noticeable slowdowns for other disk-intensive operations happening simultaneously. Schedule full backup runs for overnight or idle periods (Advanced settings → “Save copies of files” → “Daily” keeps the backup current without generating frequent smaller backup I/O during working hours). Then supplement with more frequent saves for actively-edited critical files using cloud sync as a continuous layer.
Moving File History to a new drive
If the backup drive is replaced (old drive full, drive upgrade): Control Panel → File History → “Select drive” → choose the new drive → select whether to move the existing history to the new drive or start fresh. Moving existing history preserves the version timeline continuity — older versions remain accessible from the new drive after the move completes. Starting fresh abandons old history but begins clean on the new drive.
For significant drive upgrades (replacing a 1TB backup drive with a 4TB one): moving the history preserves the ability to restore files from before the drive change. For clearing old history that’s no longer relevant: starting fresh on the new drive is cleaner. The choice depends on how far back you realistically need to restore from.
File History vs Windows Backup (the newer interface)
Windows 11 has two backup interfaces that often cause confusion: the modern “Backup” settings page (Settings → System → Storage → Backup) and the legacy “File History” in Control Panel. They both control the same underlying feature. The Settings page is simpler; the Control Panel interface provides more configuration options. Both access File History’s backup; the Control Panel version is more complete for configuration.
Microsoft’s long-term direction for backup in Windows 11 appears to be toward a simplified settings-based interface, though the Control Panel version remains available and more configurable. For users who need the advanced settings (frequency, retention, exclusions, network drives): the Control Panel route remains the right access point regardless of which interface they use to initially enable the feature.
Practical File History maintenance
A minimal annual File History maintenance routine:
- Check that File History is still running: Control Panel → File History → status should say “File History is on” with a recent last backup date
- Check the backup drive’s available space: if under 20% free, either clean up versions or upgrade the drive
- Test a restore: right-click a file → Restore previous versions → confirm a previous version appears and is restorable. This confirms the backup is functional, not just recorded as running.
- Review included folders: Settings → Control Panel → File History → Select folders → ensure new project folders or important directories added since the last review are included
This review takes 10 minutes and confirms that File History is actually protecting what you think it’s protecting, at the depth you expect. Backup systems fail silently — the most common discovery that a backup isn’t working comes at the moment you try to restore, which is exactly the wrong time to find out. An occasional active check prevents that scenario.
File History is the most direct answer to “I want previous versions of my files” on Windows 11. It’s built-in, automatic, and handles the versioning scenario that most cloud and external backup solutions don’t: recovering a file as it existed at a specific point in the past, not just the most recent backup. Setting it up takes 5 minutes; configuring it properly takes 15; running it properly requires only the initial setup plus occasional maintenance checks. For document-intensive workflows: it’s one of the most genuinely protective things you can do for your data without significant complexity or cost.
Shadow copies and volume snapshots
File History uses Windows’ Volume Shadow Copy Service (VSS) in some configurations, particularly for files that are actively in use by applications when a backup runs. VSS creates a point-in-time snapshot of the volume that allows copying files even when they’re locked by running applications. This means File History can back up files that are currently open in Word, Excel, or other applications — a significant advantage over simple file-copy backup approaches that fail when files are in use.
If VSS isn’t functioning correctly: File History may fail to back up some files and logs errors. Check: Services.msc → Volume Shadow Copy service → should be set to Manual and starting on demand. If stopped or disabled: File History backup may not run correctly for files in use. Restart the Volume Shadow Copy service and verify File History completes a full backup cycle without errors before relying on it. See also Windows 11 Clipboard History for a related case.
The combination of automatic scheduling, version history, VSS integration for in-use files, and native Windows integration makes File History one of the most practical backup solutions available for individual users. Its specific use case — versioned recovery of personal files — is well-defined and well-executed. Keep the backup drive attached, confirm it’s running periodically, and File History quietly ensures that file accidents and content loss are recoverable rather than permanent. You might also run into Windows 11 System Restore.
