A Logfile is wxrks' word, character, and segment count and analysis for a project. It's the basis for project quotes, vendor budgets, and understanding how much of a job is genuinely new work versus content your Translation Memory can already cover. This article explains what a Logfile shows, how to read its breakdown, and how to download or create one.
💡 Who is this for? This guide is for Account Admins and Project Managers who need to read a project's Logfiles to understand word counts, TM match rates, and cost estimates before quoting a project or paying vendors within the wxrks platform.
Where to find a project's Logfiles
Open the project and click its Logfiles tab. Every Logfile ever generated for that project is listed here, with Name, Type (Pre-analysis or Post-analysis - see below), Creation Date, Targets (target language), and Workflow columns.
A coin icon next to a Logfile's name means it's the Logfile currently used for the project's costs - the one feeding the Cost Results card on the project's Costs tab. Each row's Status shows whether the count finished processing, and the eye icon opens that Logfile's summary (covered below); the download icon next to it is covered further down.
Above the list, two toggles change how repetitions are counted in every Logfile's breakdown: TM Match Over Repetition (when on, 100%/101% Translation Memory matches are no longer counted as repetitions - each one keeps its own match-tier count instead), and Non-Translatable Match Over Repetition (when on, every non-translatable segment counts as non-translatable, even if it repeats elsewhere - it's never folded into the repetition count). These live on the project's Overview page as well.
Pre-analysis vs. post-analysis
A Logfile's Type is either:
- Pre-analysis: generated before translation starts, on the original source content. It's what a quote is based on - the word/character counts a Project Manager or Quote Automation uses to price the job.
- Post-analysis: generated after the linguist or reviewer has done the work, comparing the result back against the pre-analysis Logfile. It shows the actual effort spent, which is what vendor payables are calculated from.
Reading a Logfile's summary
Click the eye icon on any Logfile to open its summary.
The Words: Source (or Target) badge shows whether this Logfile counted words from the original source content or from pre-translated target content - see Calculating Costs and Vendor Payments from Target Content for why you'd want the Target option and how it changes cost calculation.
The Net Rate Coefficients selector lets you preview this Logfile's numbers as they'd be weighted for a specific workflow step, using the Net Rate Coefficients configured for your Organizational Unit. Below that, each target language gets its own row with total Segments, Words, and Characters, plus a Details toggle for the full match-tier breakdown.
The match-tier breakdown
Click the Details icon on a language row to expand its full breakdown.
Segments, words, and characters are each broken down by:
- Total: everything in the analyzed file(s).
- Repetition: content that repeats elsewhere in the same job (unless one of the toggles above changes that).
- Non-translatable: content excluded from translation entirely.
- 101% / 100% / 75%-99% / 60%-74% / 0%-59%: Translation Memory match tiers - how closely each remaining segment matches something already in your TM, from an exact context match (101%) down to no useful match at all (0%-59%).
Every row has two columns: ALL (the raw count) and NET RATE (that count after applying the Organizational Unit's Net Rate Coefficients - the per-match-tier pricing weight used for cost and payable calculations). The NET RATE FACTOR column on the right shows that weight itself for each tier - for example, if your Organizational Unit discounts 100% TM matches to 20% of a full word's price, a segment in the 100% tier shows a Net Rate Factor of 0.20, and its NET RATE count is 20% of its ALL count. Configure these coefficients from your Organizational Unit's Net Rate tab - see All about Organizational Units.
Downloading a Logfile
Click the download icon on any Logfile's row to export it.
Choose CSV or XLSX. The Rebuild file toggle regenerates the export from the Logfile's current data before downloading it, instead of reusing a previously-generated file - use it if the project has changed since the last time this Logfile was downloaded.
Creating a Logfile manually
wxrks generates pre-analysis and post-analysis Logfiles automatically at the right points in a project's workflow, but you can also create one on demand - useful for re-checking word counts after a Translation Memory update, or for generating a Target Logfile once pre-translation is done. Open the project's options menu (the icon next to its status badge, top right) and click New Logfile.
- Logfile name: defaults to "Project Logfile {number}" if left blank.
- Exclude TM Updates After: only consider TM segments updated before a date you set - useful when you want the count to reflect your TM as it stood at a specific point, ignoring anything added since.
- Ignore Confirmed Segments and Ignore Locked Segments: exclude segments already confirmed or locked in the Editor from the count.
- Ignore Subsequent Non-Translatable(s) as Repetitions and Count 100% TM Match Over Repetition: the same repetition-counting behavior as the two toggles on the Logfiles tab, set here for this one Logfile instead of the whole project.
- Count Words From - Original (Source) or Translated (Target): whether this Logfile counts the original source content or pre-translated target content. See Calculating Costs and Vendor Payments from Target Content for when to use the Target option and how it's used for cost calculation.