Recover Lost Transactions Using the QuickBooks .TLG Transaction Log File

Last reviewed 2026-08-12 3 min read

When QuickBooks Desktop crashes before saving to the .QBW, pairing the .TLG with a .QBB backup can restore everything up to the crash point.

When QuickBooks Desktop closes abnormally, whether due to a power failure, an operating system crash, or a hard freeze, the transactions entered since the last backup are not necessarily lost. QuickBooks writes every transaction to a Transaction Log file (.TLG) in real time. By pairing that log file with the most recent good backup (.QBB), our engineers can reconstruct the company file up to the moment the crash occurred. This process requires the admin password to open the file and works only when the .TLG and the backup are a matched pair from the same company file.

How the .TLG and .QBB Work Together

QuickBooks creates the .TLG file automatically in the same folder as the working company file (.QBW). Every time a user records a transaction, QuickBooks appends an entry to the .TLG before it commits that transaction to the main .QBW database. Under normal conditions, when you create a manual backup, QuickBooks incorporates the logged transactions into the backup and resets the .TLG. This means the .TLG only contains transactions entered after the last backup was made. For the recovery to work, the .QBB backup and the .TLG must share the same lineage; if a backup was restored at any point, QuickBooks generates a new .TLG, and an old log from a previous file state will not pair correctly.

Preconditions Before You Start

Before attempting a recovery, confirm a few critical details. First, locate the most recent .QBB backup file and verify it opens without errors. Second, locate the .TLG file, which sits in the same directory as the .QBW and shares the same base filename. Third, ensure you have the QuickBooks Administrator password, as the recovered file will require it to open. Finally, copy the .QBB and .TLG files to a safe, separate folder on your local drive before proceeding, so the original files remain untouched if something goes wrong.

Steps to Restore From the .TLG and .QBB

Open QuickBooks Desktop in single-user mode on the machine where you plan to work.
Go to the File menu, select Open or Restore Company, and choose Restore a backup copy.
Navigate to the local folder where you copied your .QBB file and select it. When prompted for a location to save the restored .QBW, choose a new folder rather than overwriting any existing files.
Allow QuickBooks to restore the backup completely. Do not skip any verification prompts.
Once the restored file opens, close QuickBooks entirely.
Locate the folder where the newly restored .QBW file is saved. You will see a new, empty .TLG file that QuickBooks generated during the restore. Rename this new .TLG file to something like new.tlg.OLD so QuickBooks ignores it.
Copy the original .TLG file from your safe folder into this same directory, ensuring it has the exact same base filename as the restored .QBW file.
Reopen QuickBooks and open the restored .QBW file. QuickBooks will detect the existing .TLG, read the transaction data, and apply those entries to the company file.

Signs the Recovery Worked

When QuickBooks finishes opening the file, press F2 (or Ctrl+1) to open the Product Information window. Check the Last Transaction Date or run a quick report on a bank register to confirm the most recent entries appear. If the transactions from the crash session are visible and the file passes a manual Verify (under File > Utilities > Verify Data), the recovery succeeded.

When the .TLG Is Missing or Damaged

This workaround depends entirely on having an intact, matching .TLG file. If the .TLG was deleted, stored on a failed drive, or corrupted alongside the .QBW during the crash, standard recovery is not possible. In those cases, the transactions between the last backup and the crash point are gone from the file structure. If the .TLG itself is damaged, or if the .QBW and .TLG are both compromised, deeper QuickBooks data recovery is required to extract whatever transaction fragments remain. Our engineers can often salvage partial data from a damaged .TLG, but the yield depends on how much of the log is still readable.