1. Home
  2. Blog
  3. MS Project: 7 causes of a file that is too large, and how to slim it down

MS Project: 7 causes of a file that is too large, and how to slim it down

Published on · Pilotis

An MS Project (MSP) schedule that takes a minute to open, freezes at every change or ends up refusing to save is not inevitable. In most cases, the size of the .mpp file comes from a few well-known causes that can be fixed without touching the schedule logic. Here are the seven we see most often on industrial and construction projects, and how to deal with them in the right order.

1. A file saved over for years

An .mpp keeps traces of many operations: deleted tasks, modified views, fields created then abandoned. After hundreds of successive saves, the file grows and becomes fragile. The most effective remedy is to start again from a clean file: save a copy in MS Project XML format, then reopen that XML and save it again as .mpp. The structure is rebuilt and the size often drops sharply.

Always do this on a copy, then compare the number of tasks, the finish date and the critical path with the original file before replacing anything.

2. Too many baselines and interim plans

MS Project can store up to eleven baselines and ten interim plans. On several thousand tasks, each one adds dates, durations, work and costs, including time-phased data. Keep the contractual baseline and the latest re-baseline, archive the others in a dated copy, then clear them from the working file.

3. Time-phased data on every assignment

When resources are assigned to every task, with work contours and actuals entered day by day, the volume of data explodes. If progress is tracked as a percentage rather than actual hours, this detailed data serves no purpose: simplify assignments (generic resources, no contours) or track workload in a separate tool.

4. Objects and images in notes

Screenshots, Word documents or PDFs pasted into task notes make the file much heavier. Replace them with a link to the document stored in your shared space: the note stays useful and the schedule becomes light again.

5. Inserted subprojects and external links

Consolidated schedules with inserted subprojects, cross-project links and a shared resource pool multiply dependencies: every opening reloads the other files, and a single broken network path slows everything down. Check external links, remove those no longer used and, for a master schedule, prefer a controlled consolidation through interface milestones rather than hundreds of links between files.

6. Too many custom fields and indicators

Every formula-based field is recalculated on every task at each change. Twenty custom fields with graphical indicators on 5,000 tasks means 100,000 calculations per entry. Keep those used for reporting, remove the others, and switch calculation to manual during large updates (File, Options, Schedule, Calculation) before recalculating once with F9.

7. Excessive granularity

A 12,000-line schedule where every task lasts half a day is neither more accurate nor more readable. Beyond its size, it becomes impossible to update. Group activities at the level where you actually track progress (one to three weeks on a master schedule), delete empty tasks and summaries with no content, and keep the detail in the package schedules.

Example

Fictional example based on common cases: an industrial construction schedule of 6,800 tasks weighed 92 MB and took almost two minutes to open. After the XML round trip, removing eight old baselines, taking screenshots out of notes and clearing fifteen unused custom fields, it dropped to 21 MB and opens in seconds, with the same finish date and critical path.

Checklist before touching the file

  • Make a dated copy of the original file
  • Record the number of tasks, the finish date and the critical tasks
  • List baselines, subprojects and external links
  • Check notes containing objects or images
  • List the custom fields actually used
  • After clean-up, compare with the values recorded at the start

Scheduling support

Schedule causing trouble? A planner takes care of it.

MS Project file too heavy or corrupt, conversion to Primavera P6, clean-up, baseline: quote within 48 h, files kept confidential and deleted after the assignment.

Request a quote

The tool to take action

Schedule and milestones

The Gantt chart that shows each task on a time scale, with the milestones not to miss.

See the tool