Open an .mpp file on a Mac

Microsoft Project has never had a macOS version. Drop the file below and read the plan in Safari or Chrome - no virtual machine, no Windows licence, no signup.

Drop a file here or

Your file is never saved. It is read in memory and gone as soon as the chart is drawn.

  • .mpp .xml .mpx .mpd .xer
  • up to 10 MB
  • no signup

There is no version of Microsoft Project for macOS, so an .mpp file is opened on a Mac either by running Windows or with something that reads the format directly. The second is what happens here: the file is parsed and the schedule is drawn as a Gantt chart - hierarchy, dependencies, critical path - with no virtual machine underneath it.

There is no Mac version. That is the whole problem.

This is not a case of a Mac version being worse, or lagging behind, or missing a few features. Microsoft Project's desktop application runs on Windows and has no macOS build at all. There is nothing to buy, at any price, that puts it on your machine.

Which makes the ordinary advice useless. Every thread on the subject ends in the same place: run Windows somehow. That is a real answer for someone who plans projects for a living. It is an absurd answer for someone who was sent one file and needs to read it before a meeting.

The workarounds, honestly priced

  • A virtual machine. The standard recommendation, and it works. It also means paying for the virtualisation app, then a Windows licence, then Microsoft Project itself - three purchases - followed by a long download and an install, all to open an attachment. Expect to give up a meaningful part of your afternoon and a good chunk of disk and memory.
  • Boot Camp. Frequently suggested, and no longer possible. It only ever worked on Intel Macs; on Apple Silicon it simply does not exist. If your Mac is recent, this option is not on the table regardless of what an older article tells you.
  • A remote Windows machine. A work laptop, a colleague's desk, a cloud desktop. Effective when one is available, and entirely dependent on one being available right now.
  • Microsoft's browser-based Project. Reasonable to assume this closes the gap, but it is a separate paid subscription built for planning your own work, not for reading a file that has just arrived from someone else.
  • A Mac project-management app. Several will import a schedule, most are paid, and you are installing and learning a planning tool in order to read one document. If you genuinely plan projects on a Mac this may be worth it anyway - but it is not a reading tool.
  • Ask the sender for a PDF. Free, and often the sane move. It also costs them a favour and their attention, and what comes back cannot be expanded, collapsed or searched.

Why the browser is simpler

Every option above answers the question "how do I run Windows software" - but reading a schedule does not require Windows software. The file needs to be interpreted once, and the result needs to be drawn. Neither step cares what operating system you are on, and both can happen before you finish reading this sentence.

So: drop the file in Safari, Chrome or Firefox and the plan appears. Nothing is installed on your Mac, no licence is involved, and no account is required. The file is read in memory and never written to disk - reload the page and it is gone.

Nothing about this is specific to .mpp either. A Project .xml export opens the same way, and so does a Primavera .xer if the sender plans in P6 rather than in Project - both are Windows-first tools, and both reach Macs with nothing on them that will open the file.

What comes back is the real structure, not a picture of it: phases you can collapse, dependency arrows, the critical path, non-working days shaded from the project calendar, a searchable task table, and a click on any bar for its dates, progress, predecessors, resources and notes. It is read out of the file rather than recalculated, so the dates match what the sender sees on Windows. Only the styling is ours. If what you need is the task list rather than the chart, the same read also produces an Excel spreadsheet.

The workarounds exist to get interaction back

Look again at what a virtual machine is actually buying. Nobody installs Windows, then Microsoft Project, on a Mac in order to look at a static picture of a schedule - for that, a PDF from the sender would do, free and immediately. The whole cost is paid for interaction: to fold the plan down to the phase you care about, to change the scale, to click a task and see what it depends on.

This matters when choosing between browser-based options, because most of the free ones give you exactly the thing that would not have justified the virtual machine: the plan rendered as pages you scroll, with a PDF at the end. You have avoided the Windows licence and lost the reason you wanted Windows.

What runs in your browser below is the interactive part - day, week, month and quarter scales, collapsible phases, clickable tasks with their dates, predecessors, resources and notes, dependency arrows and a highlighted critical path - on macOS, with nothing installed and no virtual machine underneath it. There is no daily file limit either, which is the other thing people hit once the schedule starts arriving in revisions. If the file has not reached you yet, the sample plans behave exactly the same way.

Common questions

Is there a Mac version of Microsoft Project?
No. The desktop application runs on Windows only, and this has been true for the entire modern history of the product. There is no Mac build to buy at any price.
Can I use Boot Camp on an Apple Silicon Mac?
No. Boot Camp only ever worked on Intel Macs. On Apple Silicon the remaining route to Windows software is a virtual machine, which means paying for the virtualisation app, a Windows licence and a Project licence on top.
Does Microsoft's browser version solve this?
Not for this problem. It is a separate paid subscription aimed at planning work, not a way to read a file that has just landed in your inbox from someone else.
Will the chart look the same as it does in Project on Windows?
The structure will: the same task hierarchy, the same dates, durations, dependency arrows, critical tasks and non-working days, because all of it is read out of the file rather than recalculated. The styling is ours, not a pixel copy of Microsoft's.