Convert PDF to ESX: Turn a Carrier Scope PDF Into an Import-Ready Xactimate File

What is PDF to ESX conversion?

What a PDF to ESX converter does

A PDF to ESX converter is the step between a carrier's scope-of-loss PDF and a working Xactimate estimate. Xactimate cannot open a PDF; it opens .esx project files that hold the folder tree, line items, quantities, trade and activity codes, F9 notes, and claim header. A converter reads the PDF and rebuilds that structure so the estimate becomes editable instead of a document you can only read. ESXPress reads each line with its quantity and the price printed on the page, maps the line to a Xactimate SEL code where one matches, and keeps your printed price where it does not. The finished .esx carries no price-list name, tax block, or minimums, so nothing is repriced until you import it and your own copy of Xactimate applies your regional list.

How to convert a PDF to ESX for Xactimate

What comes back in the .esx file

You get a Xactimate-native .esx that opens as a working estimate, not a screenshot of one. The folder tree is rebuilt, so levels, rooms, and groups organize the scope the way Xactimate expects. Each line item carries its quantity, unit, and selector code where one matched; where no code matched, the PDF's own printed price stays on the line and the line is flagged. F9 notes ride along with the lines they explain, and the claim header is preserved. The file carries no price-list identity of its own — no price-list name, no tax block, no minimums — so your import prices every matched line from your regional list. In the dashboard, the completeness layer reports the carrier's omissions before you download.

PDF vs. scope XML: which converts cleanest

Scope XML is the cleanest input when you have it. A structured export — Xactimate's own XML, the ScopeJSON v1 mirror, or another estimating system's XML — is read as data, so there is no page extraction and nothing has to be inferred from layout. Rooms, line items, and notes arrive as fields and carry through exactly as written, which is why the converter recommends XML whenever both formats exist. A PDF converts through the same pipeline with extraction and flagging, so a scope that only ever arrived as a PDF is never a problem. Either way, one rule holds: a line the converter can read is mapped and priced for import; a line it cannot verify keeps its printed price and is flagged. A file with nothing readable in it is refused with a clear message rather than turned into a mangled estimate.

What you get

What we restore that the carrier left off

Most converters stop when the PDF has been transcribed. ESXPress treats that as the halfway point. While competitors convert what is already on the page, the dashboard conversion runs a 93-rule completeness check against the finished scope and shows the citation behind every flag: the code-level reasons a line the carrier omitted should be on the estimate. That is the difference between getting the carrier's numbers into Xactimate and getting the estimate you actually need to build the job. The convention is deliberately conservative: nothing is added silently, no price and no code is invented, and every flag is shown with its citation so you decide what to include. The printed PDF stays the source of truth for pricing; the audit only surfaces what is missing from it.

Who converts PDFs to ESX this way

The people who need a PDF turned into an ESX are the ones who received the carrier's estimate as a document instead of a file. Roofing and restoration contractors get an adjuster's scope as a PDF and need an editable estimate before they can supplement it. Public and independent adjusters re-key carrier scopes to work them. Water-mitigation and large-loss teams rebuild multi-trade scopes that run to hundreds of lines. Estimating shops and supplement writers run steady volume and care about per-file cost and line-item caps. What they share is the bottleneck: retyping a carrier estimate into Xactimate by hand runs three to six hours on a large file and invites typos in codes and quantities. A conversion collapses that to about two minutes and leaves the review, not the re-entry, as the first real task.

Pricing

Multi-branch teams, carriers, and high-volume operations: custom quotes, contact us.

Free plan: 5 conversions a month, no card  ·  Paid plans: 14-day free trial (card required, no charge until it ends)  ·  Pay-as-you-go credit packs: $29 (1 file) to $375 (25 files)  ·  See full pricing →

How ESXPress compares to other PDF to ESX converters

Every tool in this category does the same first thing: read the PDF and write an ESX. The differences that actually decide the job are the conversion model (self-serve software vs. a done-for-you service that emails you a file), the published price and how it scales with volume, the line-item cap, and — the axis nobody advertises — what happens to the lines the carrier left off the scope. The table below sets the main options side by side on those axes. Rival figures are public pricing as of the dates shown and are not ours to verify beyond that; ESXPress figures are its own live tiers, verified on esxpress.org/pricing. ESXPress is independent of Verisk and Xactware, so the only claim here that is ours to make in our own voice is the final column.

Rival pricing is a dated public snapshot (see the source on each row) and may have changed; the comparison hub carries the head-to-head pages.

Proof: what a conversion actually does

Free tools around the conversion

The conversion sits inside a set of free surfaces that answer the questions around it. The Xactimate code reference describes what each SEL code is and the units it is measured in. The ESX Validator checks a file before you send it, the reprice checker shows which lines carry a code the catalog recognises, and what an ESX file is explains the format itself. The glossary covers the vocabulary the whole way (ESX, ESX file, import-ready, selector code, encrypted ESX file), and the background reading is at how PDF-to-ESX conversion works, the batch workflow, where your scope data goes and what a conversion costs. Volume and API conversions run through integrations.

Common questions

Pricing verified October 3, 2026 from esxpress.org/pricing; conversion figures are the site's own published claims. Rival figures are dated public snapshots. Xactimate is a registered trademark of Verisk Analytics, Inc. ESXPress is an independent tool and is not affiliated with, sponsored by, or endorsed by Verisk Analytics, Inc. or Xactware Solutions, Inc. Also see the comparison hub.