Recover Transactions From a .TLG File When the .QBW Is Damaged

Last reviewed 2026-08-08 4 min read

When the .QBW will not open but a recent .QBB backup exists, the matching .TLG file can fill the gap between that backup and the crash, recovering every transaction in between.

When a QuickBooks Desktop company file (.QBW) becomes damaged and will no longer open, the transaction log file (.TLG) created alongside it can often recover the work entered between the last successful backup and the point of failure. The .TLG stores a sequential record of transactions that have not yet been permanently written to the main .QBW. By pairing the last good .QBB backup with its matching .TLG, our engineers can reconstruct the missing entries and produce a working company file. The process requires the QuickBooks Admin password for the backup, because the restored file inherits the same admin credentials as the original.

What the .TLG File Actually Contains

QuickBooks creates a .TLG file automatically in the same folder as the .QBW. Every time a transaction is recorded, edited, or deleted, an entry is appended to the .TLG before it is committed to the main database. Under normal conditions, these entries are cleared each time a verified backup is produced. If the .QBW is damaged before the next backup runs, the .TLG still holds everything entered since that last backup.

The key requirement is that the .TLG and the .QBB must be a matched pair. The .TLG must originate from the same company file that produced the backup, and it must be the most recent one available. A .TLG from an earlier session, or one that belongs to a different company file entirely, will not apply.

Preconditions Before Starting

Before attempting recovery, confirm the following:

The last known good .QBB backup file is available and will restore cleanly on its own.
The .TLG file sitting next to the damaged .QBW has not been renamed, moved, or overwritten.
The QuickBooks Admin password for the .QBB is available, as the restored file will require it.
QuickBooks Desktop is installed at the same version year (or newer) as the one that created the .QBW.
The recovery should be performed on a copy of the files, never on the originals, so the damaged .QBW and its .TLG remain untouched if something goes wrong.

Copy the .QBB and .TLG into a single working folder on a local drive before proceeding. Network paths can introduce timing problems during restore and log application.

The Recovery Process

Create a working folder. Place a copy of the .QBB backup and the matching .TLG in the same local folder. Ensure no other .TLG files are present in that directory.
Restore the .QBB. Open QuickBooks Desktop, choose Open or Restore Company, select Restore a backup copy, and browse to the .QBB. When prompted for the restore location, choose the same working folder. Enter the Admin password when asked.
Allow the .TLG to apply. QuickBooks detects the .TLG in the same folder as the restored .QBW and applies the pending transactions automatically during the restore. This step is silent — there is no separate prompt for it. If the .TLG is intact and properly matched, the restored file will contain every transaction up to the moment the .QBW failed.
Run Verify and Rebuild. Open the restored file, press F2 to confirm the product information and file size, then run Verify Data from the File → Utilities menu. If Verify reports problems, run Rebuild Data and verify again.

Signs the Recovery Worked

The restored file should open without errors, the Admin password should function as it did on the original, and a spot-check of recent transactions — invoices, deposits, bill payments — should show entries dated after the .QBB backup was created. Running Verify Data without errors is the strongest indicator that the file is structurally sound.

When the Workaround Is Not Enough

If the .TLG itself is damaged, truncated, or belongs to an earlier backup cycle, the transactions between the last backup and the crash may not be fully recoverable through this method. In cases where the .QBB will not restore at all, or the .TLG produces errors during application, the underlying damage is deeper than a standard log replay can address. For damaged or corrupt QuickBooks company files that fail this process, a manual rebuild of the database structure may be required to extract whatever the .TLG and .QBW still hold.

Always keep the original damaged .QBW and its .TLG in a separate location until the recovered file has been verified in full and used through at least one complete accounting cycle.