Gantt chart for multiple projects: what actually works
Nearly every Gantt tool can draw several projects on one chart. That is the easy half and it is what most comparisons stop at. The half that decides whether the view is useful is different: can a task in one project drive a date in another? Very few tools can, and the ones that can charge for it or make you pay in ways that are not on the pricing page.
So the honest shape of this category is two questions rather than one. Seeing several projects together is common, free, and usually enough. Linking across them is rare, and it is the thing people actually mean when they say a tool cannot handle multiple projects.
Seeing versus linking: the question that sorts these tools
Seeing means several projects share one date axis, usually as collapsible groups you can fold away. It answers the questions most people actually have: where do two programmes collide, which one ends the quarter, and is there room to squeeze in a third. This is widely supported and often free.
Linking means a task in one project is a predecessor of a task in another, so a slip propagates across the boundary automatically. This is rare, and where it exists it tends to come with conditions.
Before you shop for the second one, it is worth being honest about whether you need it. Cross-project dependencies are most valuable when one team hands something concrete to another on a date that genuinely moves. They are least valuable when the two projects merely share people, which is a resource problem rather than a sequencing one and is solved by levelling the overload instead.
There is also a cultural argument, and it is the reason plenty of experienced planners avoid cross-project links even when the tool offers them. A hard link asserts that another team's date is mechanically yours. In practice cross-team handoffs get negotiated, not calculated, and a link that silently reschedules somebody else's work tends to be ignored or deleted. A milestone that two teams agreed on survives longer.
The options, and what each one really does
Six ways to put more than one project on a timeline. Capabilities below were checked against vendor documentation and support material on 24 August 2026. Packaging and plan gating change often, so confirm anything that decides your choice on the vendor's own site before committing.
1. Ganttile - several projects on one chart, free, no cross-project links
Ganttile renders any number of projects on a single chart, each as its own collapsible group, and you pick which ones appear from a selector in the toolbar. Fold two away to focus on one, or open all of them and look at the quarter at once. There is no project cap and no paid tier gating it.
What it does not do: cross-project dependencies. Tasks link normally inside a project. Across projects there is no link, and the supported approach is a milestone in the receiving project representing whatever it is waiting on, which you move when the other side lands. That is less automatic than a real link, and it is the honest limit of the tool.
- Best for: seeing several projects side by side to catch collisions and spot free capacity, without paying for a portfolio tier.
- Cross-project dependencies: no. Milestone pattern instead.
Pros
- Any number of projects on one chart, free
- Each project is a collapsible group, so the view stays readable
- Nothing to install, and a chart is shareable by link
Cons
- No dependencies across project boundaries
- No portfolio reporting layer on top of the chart
- Focused on timelines, so it is not a full work platform
2. Microsoft Project - the one that genuinely does cross-project links
Project supports a master project containing inserted subprojects, and it supports real task links across those subproject boundaries. You expand the subprojects inside the master, select a predecessor in one and a successor in another, and link them the same way you would inside a single plan. By default the master is dynamic, so changes flow both ways between master and subproject.
The cost is not on the pricing page. The files have to stay together, and Microsoft's own guidance is to keep the subprojects, the master and any shared resource pool in the same folder and not move them. Worse for a busy team, cross-project links mean Project needs the linked files, so opening a subproject can lock other project managers out of theirs. Organisations that run this setup end up with rules about who may open which file and when. That is a real operating overhead and it is the main reason a master project arrangement gets abandoned.
- Best for: programmes where cross-project sequencing is genuinely mechanical and somebody owns the file discipline.
- Cross-project dependencies: yes, fully.
What reviewers say about Microsoft Project
Reviewers consistently rate Project highly for scheduling depth: cross-project links, baselines and critical path handling that lighter tools do not attempt. The recurring complaints are the licensing model, the learning curve for anyone who has not used it before, and exactly the file-coordination overhead described above once a master project is shared across managers.
Summarised from G2 and Capterra reviews, read 24 August 2026.
3. TeamGantt - open several projects into one chart
TeamGantt lets you select multiple projects and opens them together on a single Gantt chart, either from the projects list or from Menu inside a project. Tasks can be moved between projects in that combined view, and you can filter workload by person or role across everything that is open, which is the practical use most people want.
It is a well-built version of the seeing case, with the workload angle handled better than most. Check current plan limits on the number of projects before committing a team, since that is where this category usually gates.
- Best for: agencies and teams who mainly need capacity visibility across concurrent projects.
- Cross-project dependencies: dependencies work within the combined Gantt view; confirm behaviour across project boundaries for your plan.
What reviewers say about TeamGantt
Reviewers describe TeamGantt as the easiest of the dedicated Gantt tools to get a team into, and the workload view across several open projects is the feature they mention most. The common reservation is the per-project pricing model, which teams say becomes the deciding factor sooner than the feature set does.
Summarised from G2 and Capterra reviews, read 24 August 2026.
4. monday.com - cross-project dependencies, on Enterprise
monday.com has a cross-project dependencies feature that lets you link tasks across project boards: you open a task's Dependent On column and tick See all projects to search beyond the current board. It has been gradually released to Enterprise customers.
Two limits worth knowing before you plan around it. It does not work on private or shareable projects, or on projects in closed workspaces, and only main projects appear in the dropdown. The community had been asking for cross-board dependencies for years before this arrived, which is a useful reminder that a heavily marketed platform can be missing the specific thing you need.
- Best for: organisations already on monday.com Enterprise that need linking rather than just viewing.
- Cross-project dependencies: yes, Enterprise, with workspace and project-type limits.
What reviewers say about monday.com
Reviewers praise the flexibility and the visual boards, and onboarding is frequently called the easiest in its category. The consistent reservations are that cost climbs with seats and tiers, and that specific capabilities turn out to sit on higher plans than expected, which is the pattern the cross-project dependency feature follows.
Summarised from G2 and Capterra reviews, read 24 August 2026.
5. Smartsheet - rollup yes, cross-sheet predecessors no
Smartsheet is strong at portfolio rollup through reports, and weak at exactly the thing this page is about. Predecessors only control rows on the same sheet. There is no cross-sheet predecessor function, and this is a longstanding gap that users have been requesting since at least 2016.
The usual workaround is a cross-sheet reference that pulls a date from another sheet into a cell. That copies a value; it does not create a dependency, so nothing recalculates and nothing moves downstream. If your plan spans sheets and you need real sequencing between them, this is a structural limit rather than a setting you have missed.
- Best for: portfolio reporting across many sheets, where sequencing lives inside each sheet.
- Cross-project dependencies: no.
What reviewers say about Smartsheet
Reviewers value Smartsheet for reporting and rollup across a large number of sheets, and for being immediately familiar to anyone comfortable in a spreadsheet. The most frequently raised limitation in project use is precisely the one above: dependencies do not cross sheet boundaries, and reviewers describe working around it rather than solving it.
Summarised from G2 and Capterra reviews, read 24 August 2026.
6. A spreadsheet - fine for seeing, hopeless for linking
A single sheet with a project column will show you several projects on one set of dates, and if all you need is collision detection that is a legitimate answer. Sort by project, colour by project, read down the weeks.
What it cannot do is move anything. Every date is a value somebody typed, so a slip in one project changes nothing anywhere, within or across projects. That limitation is not specific to the multi-project case; it is the general point at which spreadsheets stop being the cheap option, and running several projects tends to reach it sooner because there is more to keep in sync.
Multi-project support compared
Checked against vendor documentation on 24 August 2026.
| Tool | Several projects on one chart | Cross-project dependencies | The catch |
|---|---|---|---|
| Ganttile | Yes, any number, collapsible groups | No | Milestone pattern instead of links |
| Microsoft Project | Yes, master and subprojects | Yes, fully | Files must stay together; opening a subproject can lock out other managers |
| TeamGantt | Yes, open several into one chart | Within the combined view; confirm for your plan | Project count is usually where plans gate |
| monday.com | Yes | Enterprise only, still rolling out | Not on private, shareable, or closed-workspace projects |
| Smartsheet | Rollup via reports | No | Cross-sheet references copy a date, they do not create a dependency |
| Spreadsheet | Yes, with a project column | No | Nothing recalculates anywhere, ever |
Read down the third column and the shape of the market is obvious: one mature desktop application and one enterprise tier. Everything else asks you to handle cross-project sequencing by hand, which is worth knowing before you switch tools expecting to solve it.
The milestone pattern, for when links are not available
Since most tools cannot link across projects, it is worth doing the workaround properly rather than improvising it. The pattern is one milestone per handoff, placed in the project that is waiting.
- Put the milestone in the receiving project, named for what is being received rather than for the other team. "API contract available" rather than "Platform team finishes".
- Link the receiving project's tasks to that milestone as a normal internal dependency. Now everything downstream of the handoff moves together inside that project.
- Give one person the job of moving it when the other side's date changes. This is the step that gets skipped, and skipping it is what makes people believe the pattern does not work.
- Mirror it in the sending project as a delivery milestone, so both sides can see the same commitment on their own chart.
The trade is explicit: you accept one manual update per handoff in exchange for not needing a portfolio tier or a locked file arrangement. For most teams that is a handful of updates per quarter, because genuine cross-project handoffs are rarer than they feel. If you are counting dozens, that is the point at which the tools in the yes column start to earn their cost.
One thing this pattern does better than a hard link: it is visible to both teams as an agreement, and it puts the milestone somewhere both charts can show it rather than burying the relationship in a dependency arrow only one side maintains.
How to choose
Answer one question first and the list shortens dramatically.
- Do you need to see, or to link? If seeing, almost any option works and you should pick on price and readability. Ganttile does it free with no project cap.
- If you need to link, how many handoffs are there really? Under about five per quarter, the milestone pattern is cheaper than changing tools.
- If there are many, who owns the file discipline? Microsoft Project's master and subproject arrangement works, and it needs someone to enforce where files live and who opens what. Without that owner it degrades quickly.
- Are you already on an enterprise platform? Check what your existing tool gates behind its top tier before buying a second one. monday.com's cross-project dependencies are Enterprise, and finding that out after switching is expensive.
- Is it actually a resource problem? If the projects do not hand work to each other and merely share people, no amount of cross-project linking will help. That is an over-allocation question.
Common questions about multi-project Gantt charts
- Can one Gantt chart show several projects at once?
- Yes, and this is widely supported. Ganttile renders any number of projects on one chart, each as a collapsible group chosen from a toolbar selector, and TeamGantt lets you open several projects into a single chart from the projects list. The harder capability is not displaying them together but linking tasks across the boundary between them.
- Which tools support dependencies between different projects?
- Microsoft Project supports real cross-project task links through master projects with inserted subprojects, and monday.com has cross-project dependencies on its Enterprise plan, still being gradually released. Smartsheet does not support predecessors across sheets at all. Ganttile does not support cross-project links either and uses a milestone in the receiving project instead. Confirm current behaviour on the vendor's site, since plan gating in this area moves.
- What is the workaround if my tool cannot link across projects?
- Put a milestone in the project that is waiting, named for what it receives, and link that project's own tasks to it as normal internal dependencies. When the other side's date moves, one person moves the milestone and everything downstream of it inside that project moves automatically. It costs one manual update per handoff and it works in any tool that has milestones.
- Do I actually need cross-project dependencies?
- Less often than it feels. They matter when one team hands something concrete to another on a date that genuinely moves. If the projects simply share the same people, that is over-allocation rather than sequencing, and linking the projects will not fix it. Counting your real handoffs before shopping usually shortens the list to a number the milestone pattern handles.
Where to start
Count your real handoffs before you compare anything. Not the projects, not the tasks: the specific moments where one project cannot proceed until another delivers something. Most teams who arrive at this question expecting a portfolio problem find three or four of them.
At that number, put the projects on one chart so you can see the collisions, use a milestone for each handoff, and keep the money. Above it, and with somebody willing to own file discipline, a master project arrangement is the mature answer and has been for a long time.
Breeze
Timen
