n-What Is a QuickBooks TLG File?
A .TLG file is QuickBooks Desktop's transaction log, a running record of every change made to your company file since the last backup. QuickBooks creates and updates it automatically in the same folder as your .QBW company file, and uses it to recover transactions entered after your last backup if QuickBooks or your computer crashes before you could save.
How the .TLG file actually works
1. It's created automatically, you never touch it. The first time you open a company file, QuickBooks creates a matching .TLG file beside it with the same name. There's no setting to turn this off and nothing to configure.
2. It logs every change in real time. Every invoice, bill, payment, or edit gets appended to the .TLG as it happens, not only when you manually save.
3. It's what crash recovery actually relies on. If QuickBooks or Windows crashes before a backup, reopening the company file lets QuickBooks replay what's logged in the .TLG back into the .QBW file, recovering work that would otherwise be gone for good.
4. It resets at every full backup. Each time you run a verified local backup, QuickBooks clears the .TLG back down to near nothing, because everything logged up to that point is now safely captured inside the backup file too.
5. Large size almost always means overdue backups. A .TLG that's grown to hundreds of megabytes or more usually means a real backup hasn't run in a long stretch, weeks or months, so every transaction since then is still piling up uncleared.
What to actually do about a .TLG file that's gotten out of hand
Don't delete a large .TLG file on its own, without a recent verified backup it's the only record of everything entered since that backup, and deleting it throws that recovery safety net away for nothing. The real fix is to run a full, verified backup now; once that's done, the .TLG naturally shrinks back down because there's nothing left in it that isn't already safely backed up elsewhere.
The underlying pattern is almost always the same: backups happen when someone remembers, not on any real schedule, so the gap between backups, and the .TLG sitting there growing, stretches longer than anyone intended until the file size itself becomes the thing that finally gets noticed.
What we've built on top of QuickBooks Desktop file management
Backups that run on a real schedule
A verified backup job runs automatically on a set cadence, local or cloud-synced, so the .TLG never has months of ungoverned growth sitting behind it and nobody's relying on memory to trigger it.
An alert before file size becomes a real problem
Company file and .TLG size get checked on a schedule, with a flag to someone before growth turns into a performance issue or a crash-recovery risk, instead of it surfacing for the first time during an actual crash.
How long has it actually been since your last verified backup?
Tell us how backups currently happen in your business, and we'll tell you honestly whether that schedule is tight enough or just hoped-for.
Relying on someone to remember to back up QuickBooks?
Tell us how backups are actually handled today, and we'll tell you whether that can run itself instead of depending on someone's memory. Backups are just one example of manual upkeep; n-frames automates whatever's manual in a business, any tool, any process, not only this one.
Let's talk