How to Open a SQL Server .bak FileA .bak File Is a SQL Server Backup
A .bak file holds a full copy of a database, ready to be restored to a server. This guide explains what is inside a .bak, why it does not always restore and how to open one with or without SQL Server.
The Basics
A .bak file is the output of a SQL Server BACKUP command. It packs an entire database, its data and its log, into one file that a server can restore later. The extension is .bak by convention, not by rule, so other programs use it too.
A SQL Server backup is wrapped in Microsoft Tape Format, known as MTF. Inside that wrapper sit the database pages, the same 8 KB pages found in an MDF, along with the transaction log. Read the wrapper and you can reach the data without a restore. This physical page copy is what separates a BAK from the logical BACPAC export format.
SQL Server can write a backup plain or compressed. Compression is on by default on many servers and wraps the MTF stream in a proprietary container. Most tools that read backups handle only the plain form, so a compressed .bak stops them cold. Univik reads both.
Broad coverage
Univik reads every common backup, from plain files to MS_XPRESS compression at any transfer size and the ZSTD compression added in SQL Server 2025. A recovery mode also reads damaged and truncated backups.
There are two paths. Restore it to a running server or read it straight from the file.
With SQL Server
If you have a running SQL Server, restore the backup with RESTORE DATABASE or the wizard in SQL Server Management Studio. The database comes back live, ready to query.
Without SQL Server
If the server is gone, the restore fails or you only need the data, Univik opens the .bak directly. It reads the tables inside and exports them, with no instance and no restore.
A restore can fail for a few reasons. When RESTORE will not run, reading the backup as a file is the way through.
Newer Version
The backup came from a newer SQL Server than yours.
Damaged File
The backup is corrupt and the restore stops partway.
Compression
It uses a compression mode your server does not accept.
Encryption
The backup is encrypted and the key is missing.
The Tools
Univik reads a .bak as a file, so you get the data even when a restore is off the table.
SQL BAK Converter
Open a .bak and export the tables to CSV, Excel, SQL, JSON and more, with no restore needed. Reads compressed and plain backups.
Convert a .bak FileSQL Backup Recovery
For a damaged or suspect backup, recover the data at a low level, then export it clean. The right path for a .bak that will not restore.
Recover a Backup
Help & Support
Common questions about SQL Server backup files.
A .bak file is a SQL Server database backup, created by the BACKUP command. It holds a full copy of a database so it can be restored to a server later. Some other programs also use the .bak extension for their own backups.
Use a tool that reads the backup as a file. Univik opens a .bak directly, lists the tables inside and exports them to CSV, Excel or SQL, with no SQL Server and no restore.
Yes. Univik reads the MS_XPRESS compression SQL Server uses at every transfer size and the ZSTD compression from SQL Server 2025, not just plain backups.
Common reasons are a backup from a newer SQL Server than yours, a damaged file or a compression mode your server does not accept. When a restore fails, reading the backup as a file often still recovers the data.
No. An MDF is the live data file a running database uses. A .bak is a backup, a packaged copy of that data plus its log, meant for storage and restore. Univik reads both.
Often yes. Univik reads the backup at a low level, so it can pull data from a file that will not restore. For heavily damaged backups, run Univik SQL Backup Recovery first.