Set up a gantt chart on this computer

By Prairie Loom editorial team · Last verified September 15, 2026 · Verified against the current GanttProject release on GitHub Releases

Pick the OS tab first

Use the install panel on the home page to preselect your OS. Windows should take ganttproject-*.msi. macOS should take the matching DMG or Homebrew. Linux should take the deb. That is the whole decision tree for a standard gantt chart install.

If you are on a managed PC, confirm that MSI or Homebrew installs are allowed before you download.

Chromebooks and pure web kiosks are the wrong device class for this desktop gantt chart.

brew install --cask ganttproject

sudo apt install ./ganttproject_*_all.deb

Windows details

Check Settings → System → About for edition and architecture. The published MSI targets everyday 64-bit Windows. After install, pin GanttProject if you will rebuild the gantt chart often.

Store project files outside the Downloads folder so cleanup scripts do not erase your schedule.

When SmartScreen appears, verify the file name before continuing.

macOS details

Apple Silicon machines should prefer the silicon DMG when downloading manually. Intel Macs need the intel DMG. Homebrew’s cask selects the right bottle flow for you when you trust that channel.

Drag the app from the DMG to Applications if that is the upstream pattern on the disk image you received.

First launch may ask to open an app from the internet; that is expected for a fresh gantt chart install.

Linux details

Debian, Ubuntu, and Mint users can install the _all.deb from Releases. Other distributions may run the vendor package differently; this guide does not invent snap or flatpak ids without verification.

If your desktop lacks a deb installer GUI, use apt install on the local file as shown in site config.

Confirm the app launches from the menu and can save a .gan file.

Prove the install

Create three tasks, link two of them, and export a PNG. That proof matters more than browsing every toolbar icon on day one.

Only then import an old plan or connect optional collaboration features.

If launch fails, revisit the download-safe page before trying a second mirror.

Team rollouts

Document the asset pattern in your internal wiki: MSI for Windows gantt chart hosts, cask for Macs, deb for Linux build machines.

Avoid silently mixing EXE and MSI across the same team without a note.

Point people at /installed for the first-hour checklist.

Keep the job name clear

Keep the write phrase clear when you talk about the job: people typed gantt chart because they need bars on a timeline, not a slide deck sketch. GanttProject is the GPL-3.0 program this guide installs, and the official binaries live on GitHub Releases under ganttproject-* tags. Prefer ganttproject-*.msi on Windows, match silicon or intel DMG files on macOS, or install the Homebrew cask when that is your standard Mac channel. Linux users on Debian-family desktops should take the architecture-independent deb from the same tag and install it with their usual package tool.

One careful install

A careful install habit beats a clever workaround. Download once from bardsoftware/ganttproject, verify the file name, run the installer, and prove a tiny schedule before you import a giant plan. Save a .gan file in a folder you back up. Export a PDF or PNG so stakeholders can read the gantt chart without installing the desktop app. When you update, return to the same Releases page rather than a random mirror that wraps the setup in unrelated offers.

Dependencies first

Dependencies are what make a gantt chart honest. If you only paint bars without links, a slip in one task never moves the work that should wait. Add finish-to-start links on day one, mark milestones for fixed events, and set a baseline before a major reshuffle so you can compare plan versus actual. Resource load charts help after the timeline itself is trustworthy. Cost fields help when money tracks with time. None of those extras replace clear task names and realistic durations.

Release metadata

The install panel resolves official assets through the latest fetched release metadata. Versions in the footer and stamp come from that data at build time, so you should not pin a version number in your internal prose if you can say “current release on GitHub Releases” instead. Winget was not verified for GanttProject on the research day, so Windows stays on the MSI path. Homebrew’s ganttproject cask was verified via formulae.brew.sh for macOS.

When something fails

If something fails, stop and re-check the download-safe steps before you try a second website. SmartScreen and Gatekeeper prompts are normal for first launches of internet-downloaded software. Continue only when the publisher and file name match what you expect from the bardsoftware release. Share the Releases URL with teammates instead of emailing a private copy of the MSI that will go stale.

Ongoing work habits

For ongoing work, treat the schedule like any other engineering tool: one update door, one project folder convention, one person who checks Releases after a major planning cycle. Optional WebDAV or GanttProject Cloud collaboration can wait until offline scheduling is boringly reliable. Importers for MS Project and spreadsheets are power tools—prove a native file first, then migrate, then clean links that did not survive.