whatfileis.pro
Paste a filename and find out what it is, whether it is safe, and what opens it.

Are .bak Files Safe to Delete?

Short answer: yes, a .bak file is usually safe to delete — but only after you confirm the live file it backs up is intact. A .bak is a copy of an earlier version; deleting it just removes your ability to roll back to that point.

Category
Safe to delete?
Opens with

The verdict

Safe to delete once you have confirmed the current file is fine. A .bak (backup) file is a copy an application makes before it saves or overwrites the original — editors, CAD programs, databases and games all do this. Its only job is to let you restore the previous version if the new save goes wrong. When the live file opens and works, the .bak is spare, and you can reclaim the space.

Before you delete

A .bak is only a backup if the real file still exists. Occasionally a .bak is the only surviving copy of something — for example your app crashed mid-save. So first confirm the matching live file opens correctly, then delete the backup. Keep the most recent .bak as a safety net on anything important.

A couple of exceptions

  • SQL Server backups (.bak database dumps) are real restore points, not disposable scratch — only delete old ones you have a newer backup for.
  • Office 2003 keeps a system file OPA11.bak; deleting it can break the install. Leave .bak files inside program folders alone.

How to delete them

  1. Confirm the matching document/project opens and looks correct.
  2. Delete the .bak next to it, or search the folder for *.bak and remove the old ones.
  3. To stop them coming back, turn off "create backup copy" in the app's save settings — though keeping it on is usually wise.

Is a .bak file a virus?

No. A .bak is inert saved data, not executable. Renaming it back to its original extension restores a working file, so it is only as risky as whatever it is a backup of.

FAQ

Are .bak files safe to delete?

Usually yes, but only after you confirm the live file it backs up opens correctly. A .bak is a copy of an earlier version; deleting it just removes your ability to roll back.

Is a .bak the only copy of my file?

Sometimes — if an app crashed mid-save, the .bak may be the newest surviving version. Always check the matching live file exists and works before deleting the backup.

Are SQL Server .bak files safe to delete?

Those are real database restore points, not scratch files. Only delete old .bak backups you already have a newer backup for, and never the one you may need to restore from.

Is a .bak file a virus?

No. A .bak is inert saved data, not runnable code. It is only as risky as the original file it is a backup of.

Other file types explained