File-level backup in Windows for a new PC or drive

A file-level backup in Windows means copying the files and folders you actually want to keep, instead of making a full clone of the whole system. For a move to a new PC or a drive replacement, start with your personal folders first, then add app-specific data only when it contains something you cannot easily replace. In practice, that usually means your documents, photos, desktop files, and a few special folders such as mail stores, browser profiles, or game saves.

What a file-level backup in Windows actually means

A file-level backup is a copy of chosen files and folders, such as a folder full of work documents or your photo library. It is not the same as a full system image, which tries to preserve the whole Windows installation, apps, settings, and the boot structure together.

That difference matters because file-level backup is about migration and recovery of your own data, not preserving the old PC exactly as it was. If you are moving to a new computer, replacing a failing drive, or making room for a clean install, file-level backup is usually the faster and cleaner option. You choose what matters, copy it somewhere safe, and leave the rest behind.

For example, say you only need your writing drafts, tax PDFs, and family photos. You do not need to copy the entire Windows folder or every installed program just to move those files. You only need the folders where those items live, plus any app data that stores something you cannot recreate easily.

If you only copy one thing first, copy your personal folders

Start with the folders Windows already uses for your own files. On a typical PC, that means Documents, Desktop, Pictures, and Videos. If you have music, keep Music too. These folders are the fastest way to preserve the things people notice immediately after a migration.

A practical first pass looks like this:

• Documents for work files, school work, notes, and PDFs
• Desktop for files you parked there temporarily and forgot about
• Pictures for photos, screenshots, and edited images
• Videos for home movies, recordings, and exported clips
• Music if you still keep a local library

If you are short on time, copy these folders before anything else. They are usually the highest-value data with the lowest risk. Even if you later find a forgotten app setting or browser profile, your main personal files will already be safe.

What belongs in a normal Windows file backup

A normal file-level backup usually includes anything that would be painful to recreate by hand. That means office files, PDFs, spreadsheets, image libraries, project folders, notes, and downloaded installers or archives you still need.

A good rule is to include files that are one of these:

• Created by you
• Edited by you
• Saved from email or the web and still needed
• Hard to redownload because the source may be gone
• Tied to ongoing work, school, or personal records

Typical examples are tax documents, receipts, client files, manuscripts, screenshots, exported reports, scanned papers, and ZIP files that contain old project assets. If you keep a shared folder outside the usual Windows libraries, include that too. Many people store important files in custom folders under C:\Users\YourName\ or on a second drive, so check any place you used as a catch-all over the years.

Downloads is a special case. A lot of what lives there can be thrown away, but keep the items you have not installed, opened, or organized yet if they still matter. That folder often contains installers, PDFs, bank statements, and one-off files that never got moved anywhere else.

What to copy from AppData and where people usually miss it

AppData is where many Windows apps store settings, profiles, caches, and local data. It lives under your user profile, usually at C:\Users\YourName\AppData\. There are three parts: Roaming, Local, and LocalLow. Not every app uses them the same way, so you do not need to copy the whole thing blindly.

The places people most often miss are browser profiles, mail data, and app preferences. Some desktop tools keep templates, dictionaries, macros, custom presets, or saved sessions in AppData. A browser profile can hold bookmarks, extensions, history, cookies, and sign-in state. Some mail clients store account data or local message files there as well.

Copy AppData only when you know the app uses it for something you want to keep. Good examples include:

• Browser profiles if you want local settings or offline data
• Mail profiles or local mail stores for desktop email apps
• Creative apps with custom brushes, presets, or templates
• Specialist tools with databases, configurations, or saved sessions

Be careful with the whole folder. AppData also contains temporary files and caches that you do not need. If you are unsure, back up the specific app subfolder rather than the full tree.

For browser data, check the browser’s own sync first. If bookmarks, passwords, extensions, or history are already syncing to a Microsoft, Google, or Firefox account, you may not need to copy the whole profile. Copy the profile only if you want local-only state, offline data, or a fallback in case sync is incomplete. If you use a browser that does not fully sync what you care about, copying the profile folder is still the safer move.

For app data in general, the question is not whether AppData is “important” in the abstract. It is whether that specific app stores something you would have to rebuild by hand. If the answer is yes, back up that app’s folder. If the answer is no, skip it.

What you can usually skip

You can usually leave out anything Windows or the app can rebuild, reinstall, or redownload. That includes most installed programs, many caches, temporary files, logs, and update files. If the app is easy to reinstall and does not keep unique local data, copying its install folder is usually wasted effort.

Common things to skip are:

• Program installation folders under Program Files and Program Files (x86)
• Temporary folders such as Temp
• Browser caches and other throwaway cache data
• Windows update files and system restore data
• Thumbnails, logs, and crash dumps

Steam, Microsoft Store apps, and many launchers can redownload their own program files. Windows itself can also recreate a lot of system data after a reset or fresh install. That is why a file-level backup should focus on the things only you can restore: your work, your photos, your personal records, and any app data that would take time to rebuild by hand.

One caution: skipping something because it looks replaceable is fine only if you are sure you do not need the local data inside it. A game folder may be mostly redownloadable, but the save files inside it may not. The same goes for portable tools, plugin folders, and custom configuration files. If the folder contains your settings or history, back up that part even if the program itself can be installed again.

How cloud sync changes what you need to back up

Cloud sync changes the job, but it does not remove it. If your files already sync with OneDrive, Google Drive, Dropbox, or a similar service, some of your data may already be copied elsewhere. That means you may not need to back up every synced folder again, especially if the cloud copy is current and complete.

The catch is that sync is not the same as backup. Sync copies changes between devices, so if a file is deleted, renamed, or corrupted everywhere, the sync service may follow that change. Also, not every folder on the PC is part of sync. Many desktop files, app settings, downloads, and local-only project folders are still outside it.

A sensible approach is:

• Check which folders are actually synced
• Confirm that the files you care about are present in the cloud copy
• Back up anything outside those synced folders
• Back up local copies of important files if you are not sure the sync finished

For example, if Documents is inside OneDrive on your old PC, those files may already be available on the new PC once you sign in. But if you kept a separate folder on D:\Projects, that folder needs its own backup. Do not assume sync covers the whole machine.

Synced cloud folders are worth a quick check before you copy them twice. If the folder is already fully synced and you can verify the files online, you can usually leave that copy out of the local backup. If the sync status is unclear, back it up anyway and sort it out later.

Special cases that deserve a closer look

Some data does not live in the obvious Windows folders, and that is where people lose time during a move. Outlook is a common example. If you use classic Outlook with local data files, your mail, archive, or offline content may be stored in a PST or OST file. PST files are the ones people most often need to keep. The exact setup depends on how the account was configured.

Browser bookmarks deserve a check too. Modern browsers often sync them, but if you do not trust sync or use an older profile, export them or copy the browser profile folder. That is especially useful if you rely on extensions, saved passwords, or offline profile data.

Game saves can live in several places: inside Documents, inside AppData, or in a game-specific folder. Some games also sync saves through the launcher or platform, but not all do. If a save file matters to you, look for the game’s own save location before you wipe anything.

Old project folders are another case worth checking. Creative software, coding projects, and hobby tools often store dependencies, templates, or asset caches in a project tree that you may not want to rebuild from scratch. If a folder took you time to organize, back it up even if it is not in a standard Windows library.

Two more special cases are worth calling out. First, local email archives: if you used Outlook or another desktop mail app with downloaded mail, those message files can be more valuable than the app itself. Second, synced folders that are also used offline: if you worked in a cloud folder while disconnected, wait until the sync client finishes before you assume the latest version is safe.

A simple order for moving to a new PC or replacing a drive

The easiest order is: personal files first, app data second, reinstallables last. That keeps you from spending time on things you can replace later.

1. Copy your core personal folders: Documents, Desktop, Pictures, Videos, and Music if you use it.
2. Copy any custom work folders, project folders, and data stored outside the standard libraries.
3. Check Downloads for files you still need, such as installers, PDFs, or archives.
4. Back up app-specific data only for the apps you actually care about, especially mail, browser profiles, presets, and save files.
5. Leave program files, caches, and other rebuildable items until the end, or skip them entirely.

If you are replacing a drive, do the copy before you erase or repartition the old one. If you are moving to a new PC, copy to an external drive or cloud location first, then bring the files across once the new machine is ready. That order lowers the chance of missing a folder that turned out to matter.

How to check that your backup is actually usable

A backup is only useful if you can open the files and find them again later. Before you wipe the old drive or reset the PC, check a few files from each important folder. Open a document, view a photo, and make sure one or two videos or PDFs play or display correctly.

Also compare folder names and size by eye. You do not need a perfect audit for a normal move, but you do want to notice obvious gaps, such as an empty Pictures folder or a missing project directory. If you copied app data, confirm that the expected file types are there, such as PST files, browser profile folders, or game save files.

A quick sanity check helps more than people think:

• Open several files from different folders
• Confirm the files are readable, not just present
• Check that the backup location contains the folders you expected
• Make sure the files are not only in a sync queue or partial upload state

If something looks off, fix it before you move on. It is much easier to copy one missing folder now than to recover it after the old drive is gone.

Conclusion

If you want the shortest safe path, start with your personal folders, then add only the app data that would be hard to recreate. Treat `AppData`, browser profiles, synced cloud folders, and special files like mail stores or game saves as case-by-case items, not automatic copies. Once the files open and the folders look right, you can move to the new PC or replace the drive with much less risk of missing something useful.

Frequently Asked Questions

Should I back up AppData in full?

Usually not. `AppData` contains useful settings and profiles, but it also contains caches and temporary data. Back up only the app folders you know you need.

Do I need to copy Program Files?

Usually no. Most installed programs can be reinstalled, and many can be redownloaded. Copy the program only if it stores unique data you cannot get back another way.

If OneDrive syncs my Desktop and Documents, do I still need a backup?

Yes, if you want protection against deletions, corruption, or sync mistakes. Sync helps with access across devices, but it is not the same as a backup.