How to open an XER file without Primavera P6 (free, in your browser)

Someone has emailed you an .xer file, you don't have a Primavera P6 licence, and the meeting is tomorrow. Good news: you can open an XER file without P6, free, and in several different ways — including in the browser tab you already have open. Here are the five routes, honestly compared, and what each one quietly loses.

The short answer first. To open an XER file without Primavera P6 you can: use a browser-based viewer (no install, free options exist); use a desktop XER viewer (paid licence, but no P6 needed); import into Microsoft Project via P6's XML format (works, but lossy); sign up for a free P6 trial (heavyweight, but it is the real thing); or parse the file as text in Excel (fine for a flat activity list, hopeless for anything else).

Which route is right depends on one question: do you just need to see the dates, or do you need to understand the logic, float and baselines behind them? If it's the former, almost anything works. If it's the latter — and if you're reviewing a contractor's programme, it should be the latter — most of the convenient routes will let you down. Let's start with what you've actually been sent.

What an XER file actually is

An XER is not a proprietary binary blob. It is a tab-delimited text export of a slice of the P6 database — a set of relational tables flattened into one file. The big ones are TASK (the activities), TASKPRED (every relationship in the network), PROJWBS (the work breakdown structure) and CALENDAR (working time definitions), plus a dozen or two supporting tables for resources, codes and user-defined fields.

The format is simple: a line starting %T announces a table, %F lists its column names, and each %R line is one row of data. Which means yes — you can literally open an XER in Notepad or TextEdit and read it. You will quickly discover why nobody does. Durations and float are stored in hours, dates reference calendars defined hundreds of lines away, activities reference WBS nodes by internal ID, and the logic lives in a separate table keyed on numeric task IDs. The data is all there; the meaning is spread across tables that only make sense once something rebuilds the relational structure and runs the date arithmetic.

The five routes, honestly compared

1 · Desktop XER viewers

Purpose-built viewers in the ScheduleReader / PrimaveraReader mould install on your PC and read XER files natively, with good fidelity: logic, float, filters, often baselines. The catches are cost and friction — they are licensed per seat (typically a few hundred pounds a year), they need installing (a problem on locked-down corporate machines), and they are read-only by design. For a planning team that reviews contractor XERs weekly and can't justify P6 seats for everyone, they're a sensible standing tool. For "I need to look at this file today", the procurement cycle defeats the purpose.

2 · A free P6 trial

Oracle offers trial routes to P6, including cloud-hosted EPPM trials. This is the only option that gives you the genuine article — the real scheduling engine, every field, every layout. It is also the heaviest possible answer to "open this file": you'll create an Oracle account, possibly stand up a database or wait for cloud provisioning, and learn enough P6 to import an XER (itself not trivial — import options can alter calendars and clear baselines if misconfigured). Trials also expire, and using rolling trial licences for routine commercial work puts you on thin ice with Oracle's terms. Right answer if you're evaluating P6 itself; wrong answer if you just need to read a programme.

3 · Import into Microsoft Project

MS Project cannot read XER directly, but P6 can export to its XML format, and MS Project will import that (third-party converters do XER→MPP directly). If your organisation already lives in MS Project this feels natural — but the conversion is genuinely lossy. P6's multiple calendars map awkwardly onto MS Project's model, so durations and dates can shift on import. Lags defined against predecessor calendars get reinterpreted. P6 constraint types don't all have MSP equivalents, so constraints are translated or dropped. Activity codes, of which a real programme has hundreds, frequently don't survive. The result looks like the schedule you were sent, recalculated under different rules — which for any forensic or contractual purpose is worse than not opening it at all, because it's quietly different.

4 · Excel or text parsing

Because an XER is tab-delimited text, Excel can ingest it: open the file, split on tabs, find the TASK table, convert hours to days, and you have an activity list with dates and durations. For a one-off "what activities are in this programme?" exercise, that's fine, and it costs nothing. But Excel gives you no network. The logic sits in TASKPRED as thousands of numeric ID pairs; rebuilding it into anything navigable means writing what amounts to a small CPM engine in formulas or VBA. No float calculation, no critical path, no calendars, no baselines. A flat list of dates with no logic behind it is precisely the thing a bar chart printed to PDF already gives you.

5 · Browser-based viewers

The newest category: open a web page, drop the XER in, see the programme — Gantt, logic, float, WBS — with nothing to install and no licence to buy. For speed and accessibility this is the route that wins for most people, most of the time. But there is one distinction inside this category that matters more than any feature: does the tool upload your file to a server, or parse it client-side in your browser?

Many free "online XER converters" work by uploading your file to their infrastructure, processing it there, and serving results back. Think about what an XER from a live commercial programme contains: the contractor's entire delivery strategy, real progress against it, float positions, sometimes resource and cost data. Sending that to an unknown third party's server — jurisdiction unknown, retention policy unread — can put you in breach of contract confidentiality clauses before you've even looked at the dates. Client-side tools avoid the question entirely: the parsing happens in JavaScript on your own machine and the file never crosses the network. This is the approach we took with ScheduleInsight — drop an XER (or MS Project file) into the browser, it parses locally, the file never leaves your machine, and viewing is free. Whatever tool you pick, verify which kind it is before you feed it anything sensitive.

What to check, whichever route you choose

Three things separate a viewer you can rely on from a bar-chart renderer with good marketing:

• Does it read logic and float, not just bars? If you can't see an activity's predecessors, successors and total float, you can't tell which dates are calculated and which are decoration. A programme's story lives in its network — float is how the network talks to you.
• Does it show the data date? Everything left of the data date is claimed history; everything right is forecast. A viewer that doesn't display it — or a schedule that hides it — should make you suspicious of every bar on the screen.
• Can it handle baselines? A current schedule in isolation tells you what the contractor says now. The variance against the baseline tells you what's actually been happening. If the XER carries baseline data, your viewer should show it.

And once the file is open, remember that being able to see a schedule is not the same as being able to trust it. Open ends, dangling logic, hidden constraints and negative float don't announce themselves on a Gantt view — that's what a structural check like the DCMA 14-point assessment is for, and it's the natural next step once you've got the file open.