.TLG File Fix: How to Truncate Transaction Logs to Boost Performance

September 13, 2026 7 min read

The Transaction Log file (.TLG) is a companion database file that records every write, edit, and deletion made to your QuickBooks company file (.QBW) between backups. Over months or years of continuous entry, an untruncated .TLG file can balloon to 5, 10, or even 20 gigabytes—frequently dwarfing the actual .QBW data file. This bloat causes severe system lag, slow multi-user switching, long backup wait times, and startup freezes. Safely resetting and truncating the .TLG file restores operational speed without deleting transaction data.

Fast-Fix: The 45-Second Solution

To instantly truncate a bloated .TLG file safely, create a native QuickBooks local backup with full verification. In QuickBooks, go to File > Back Up Company > Create Local Backup. Select Options, choose Complete verification, and run the backup to your local drive. Once the backup finishes, QuickBooks commits the pending transactional cache and automatically shrinks the .TLG file down to under 1 megabyte.

Quick Status & Triage Snapshot

Data Risk Tier: Low to Medium. Using the native backup method carries zero data risk. Manually renaming a .TLG outside of QuickBooks carries risk only if your .QBW file suffers immediate damage before a new full checkpoint backup is created.
Multi-User Impact: Requires all users to log out while executing the truncate routine.
Common Triggers: Relying exclusively on third-party cloud/drive backups (which do not truncate logs), high-volume daily sales entries, or running without a native full-verification backup for months.
Estimated Fix Time: 5 to 15 minutes (depending on .QBW file size).

Diagnostic Flowchart: .TLG Management Decision Path

QuickBooks operations are slow / .TLG file is unusually large
 │
 ├── Compare file sizes in the company directory
 │    ├── Is .TLG larger than the .QBW file?
 │    │    └── YES ──> Transaction log requires immediate truncation.
 │    │
 ├── Can you open QuickBooks and log in as Admin in single-user mode?
 │    ├── YES ──> Run a Native Complete Verification Backup.
 │    │            ├── .TLG resets to < 1 MB? ──> Resolved.
 │    │            └── .TLG fails to reset? ──> Proceed to Manual Reset routine.
 │    │
 │    └── NO (QuickBooks is crashing or won't launch)
 │         └── Perform Manual .TLG Reset (.old extension) and run Verify Data.

Is Your Data at Risk?

Understanding the precise purpose of the .TLG file is essential for data safety.

During standard operations: The .TLG file does not contain “separate” data that is missing from your .QBW file. Every transaction entered is simultaneously committed to both the .QBW database pages and the .TLG transaction log.
When the .TLG is vital: If your core .QBW file suffers physical sector corruption or hard-drive failure, professional data recovery specialists use the .TLG file alongside your last verified backup to reconstruct transactions entered up to the moment of failure. Refer to .TLG Recovery: How to Recover Data from a Damaged Transaction Log File if you are actively rebuilding a corrupted database.
Never delete a .TLG blindly: Always rename it (e.g., .TLG.old) rather than deleting it outright, ensuring you retain the recovery fallback until a fresh verified backup is completed.

Technical Anatomy: Why the .TLG File Expands

QuickBooks relies on the Sybase SQL Anywhere transactional database engine. This engine implements Write-Ahead Logging (WAL):

[ Data Entry / Edit ]
        │
        ├───> 1. Writes changes to .TLG (Sequential Write-Ahead Log)
        │
        └───> 2. Commits changes to .QBW (Relational Database Tables)

The .TLG file serves as a ledger of changes between full backup checkpoints.

Why do .TLG files grow out of control?

Third-Party Backup Failure to Truncate: Programs such as Windows Backup, Carbonite, Acronis, or Google Drive simply copy the raw .TLG file across the network. They do not trigger the internal Sybase checkpoint command required to commit and purge the transaction log.
Incomplete Verification Backups: If users back up using “Quick verification” or skip verification to save time, QuickBooks skips the transactional commit routine, leaving the .TLG file unpruned.
Resulting Performance Penalty: When opening a company file or querying records across multi-user networks, the database engine must check and validate pointers between the .QBW and the sprawling .TLG file, causing severe multi-user lag and disk I/O bottlenecks.

Differential Diagnosis: Don’t Confuse This With…

**Manual Fix: Renaming .ND and .TLG Files to Resolve 6000-Series Errors:** Renaming .TLG alongside .ND is a specific fix for network communication errors (such as Error 6000, -83) where connection files are locked. Truncation is an intentional performance maintenance routine.
**Portable Files: Using .QBM Files to Temporarily Shrink Your Database:** Creating a .QBM file strips out images and temporary tables to create a lightweight transport file; it does not replace the primary on-disk .TLG file of your production environment.
**Database Fragments: How to Audit and Fix Fragments That Slow You Down:** Fragmentation describes non-contiguous data blocks on disk inside the .QBW file. A bloated .TLG is a single file size issue that exacerbates fragment formation.

Step-by-Step Repair Guide

Use Method 1 first. If the file refuses to shrink, proceed to Method 2.

Method 1: The Native Backup Truncation (Recommended)

This is the official, Intuit-supported method to safely reset transaction logs.

Ensure all users log out of QuickBooks.
Log into the company file as the Admin user.
Switch to Single-User Mode (File > Switch to Single-User Mode).
Click File > Back Up Company > Create Local Backup.
Select Local Backup and click Options.
Set the backup options window:
- Verify the backup directory.
- Under “Online and local backup”, select Complete verification (recommended).
Click OK, then click Next.
Select Save it now and click Finish.
Allow the backup to complete. Once finished, navigate to the folder where your company file resides in Windows File Explorer. The .TLG file will now display a size of roughly 256 KB to 1 MB.

[ Backup Options Configuration ]
  Tell us where to save your backup copies:
  Destination: [ C:\QB_Backups\ ]

  Verification Options:
  ├── ( ) Do not verify
  ├── ( ) Quick verification
  └── (*) Complete verification (recommended)  <-- MUST BE SELECTED

Method 2: Manual .TLG Reset Procedure

Use this procedure if your company file hangs or freezes when attempting to execute a backup due to an excessively large (10GB+) log file.

Have all users exit QuickBooks on all workstations.
On the host computer or server, open Windows Task Manager (Ctrl + Shift + Esc) and ensure that QBW32.exe and QBDBMgrN.exe are not holding locks on the file.
Open Windows File Explorer and navigate to your company file folder (e.g., C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
Locate the file with your company name and the .TLG extension (e.g., MyCompany.qbw.tlg).
(If file extensions are hidden, enable them under Windows File Explorer by clicking View > checking File name extensions).
Right-click the .TLG file and select Rename.
Change the name to MyCompany.qbw.tlg.old.
Also locate the corresponding .ND file (MyCompany.qbw.nd) and rename it to MyCompany.qbw.nd.old.
Do not touch the .QBW file.
Launch QuickBooks and open the company file as Administrator.
QuickBooks will automatically generate a clean, brand-new .TLG file initialized at minimum size (typically under 512 KB).
Immediately run an integrity check (File > Utilities > Verify Data) to ensure database pointers are fully synchronized.

[ Directory View Before vs. After ]
BEFORE:
  MyCompany.qbw       (450 MB)
  MyCompany.qbw.tlg   (12,400 MB)  <-- Massive bloat causing slowdowns

AFTER:
  MyCompany.qbw       (450 MB)
  MyCompany.qbw.tlg   (256 KB)     <-- Fresh, active transaction log
  MyCompany.qbw.tlg.old (12.4 GB)  <-- Safe archive (delete after 30 days)

Hard Stop: When to Call an Expert

You should halt manual adjustments and seek advanced data recovery support if:

After renaming the .TLG file, QuickBooks refuses to open the .QBW file, throwing a critical 6000-series database mismatch error.
The .TLG file re-expands by multiple gigabytes in less than 24 hours without significant data entry, indicating an automated third-party application or corrupt script is stuck in a transaction commit loop.
The company file fails the subsequent Verify Data check with unrecoverable B-tree or link-pointer errors.

Closing the Books

A bloated .TLG file is not a sign of damaged accounting data, but rather a sign that your database maintenance has fallen out of routine. By incorporating a native, verified local backup into your weekly or monthly accounting schedule, QuickBooks will automatically manage its transaction log size, keeping your multi-user network fast and responsive.

Item List Cleanup: Reducing File Overhead for Faster Processing

September 14, 2026

List Limit Reached: Troubleshooting Pro and Premier Data Constraints

September 12, 2026

QuickBooks Performance: How (and When) to Condense Your QuickBooks File

July 2, 2026