GanttChartBI: Free Browser Gantt Chart Maker (PDF & PNG)

· Apps

Originally a Power BI Deneb visual, now a standalone web app. Add tasks, set dependencies, track progress, and export polished Gantt charts to PDF or PNG. No Power BI required.

GanttChartBI started as a custom Power BI visual built with Deneb and Vega-Lite — but not everyone has Power BI. So I turned it into a standalone web app where anyone can add tasks, set dependencies, track progress, and export a polished Gantt chart to PDF or PNG.

No Power BI, No Downloads, No Signups

Just open the browser, add your tasks, and get a professional project timeline. Works entirely in-browser with local storage — your data never leaves your device.

Key Features

  • drag-and-drop task management — Simply add task name, start date, end date, and progress
  • Dependency tracking — Link tasks so one can't start until another finishes
  • Progress tracking — Mark completion percentage for each task
  • Interactive timeline — Zoom, pan, and explore your project visually
  • Export to PDF or PNG — Download polished charts for presentations and reports
  • 100% local processing — Your data stays on your device

How to Use

  1. Open the app in your browser
  2. Add tasks with names, start/end dates, and progress %
  3. Set dependencies by dragging between tasks
  4. View the interactive Gantt chart
  5. Export to PDF or PNG for your presentations

Technology Stack

  • React + TypeScript for the UI
  • D3.js for the Gantt chart visualization
  • html2canvas and jsPDF for exports
  • Local Storage for data persistence

When to Use GanttChartBI

  • Quick project planning without project management software
  • Client presentations requiring visual timelines
  • Software development sprint planning
  • Event or campaign scheduling
  • Any situation needing a quick Gantt chart without enterprise tools

Why I Rebuilt a Power BI Visual as a Web App

The original Deneb visual solved a real problem for reporting teams: Power BI has no native Gantt chart, so project timelines usually end up as a screenshot pasted from another tool. Deneb plus Vega-Lite fixed that inside Power BI, but it created a new dependency — anyone who wanted the chart needed a Power BI licence, a workspace, and a dataset shaped exactly the way the visual expected. Most of the people asking me for the chart were project managers and consultants who had none of those things. Rewriting the same rendering logic in plain D3.js removed every one of those prerequisites while keeping the layout identical.

The rewrite also made iteration far quicker. In Power BI, changing a bar corner radius or a dependency arrow meant repackaging the visual and reimporting it into every report. In the browser version the chart is a single D3 render function, so date scaling, task ordering, and dependency routing are all adjustable in one place, and the export path reuses the exact same SVG the screen shows.

How the Timeline Is Calculated

Each task is stored as a start date, an end date, a completion percentage, and an optional list of predecessor IDs. A scaleTime band spans the earliest start to the latest finish, and each row is drawn as two stacked rectangles: the full task duration in a muted fill, with the completed portion overlaid in the accent colour. Dependency arrows are drawn as elbow connectors from the right edge of the predecessor to the left edge of the successor, so a chain of blocked work reads at a glance.

Dependencies are validated when they are created. If linking two tasks would produce a cycle, the link is rejected rather than silently rendering an impossible plan. When a predecessor moves, dependent tasks are flagged, not auto-shifted — automatic rescheduling tends to surprise people mid-edit, so the app shows the conflict and lets you decide.

Exporting Without a Server

Exports run entirely on the client. The chart container is rasterised with html2canvas at two-times device pixel ratio so text stays crisp, then either downloaded directly as PNG or placed into a jsPDF document sized to the chart aspect ratio. Because nothing is posted to a backend, an export of a confidential client schedule never leaves the machine — which is the main reason finance and audit teams were comfortable using it.

Limitations Worth Knowing

Build a useful first timeline

Start with deliverables people can recognise rather than every small action. A finance reporting project might have source-data review, metric agreement, model build, reconciliation, user review and handover. Give each task a clear start and end, then add dependencies only where the successor genuinely cannot proceed without its predecessor.

Example taskPlanned periodPredecessor
Source-data review2–4 NovemberNone
Metric agreement5–6 NovemberSource-data review
Model build9–13 NovemberMetric agreement
Reconciliation and review16–18 NovemberModel build
Handover19–20 NovemberReconciliation and review

These dates are illustrative, not a delivery commitment. The picture makes sequencing visible; it does not automatically account for weekends, holidays, staff availability or task effort. Check those constraints separately when turning the timeline into a delivery plan.

Use progress consistently

Completion percentage should describe work achieved, not time elapsed. A five-day task is not necessarily 60% complete on day three. Agree how each task is measured: completed records, reviewed sections or accepted deliverables may be better evidence than a subjective estimate.

Keep the original plan separately if you need to explain slippage. Updating every finish date to today can make a late project look on schedule. If a predecessor moves, review dependent dates yourself; the app flags conflicts rather than performing full automatic rescheduling.

Prepare an export that survives a meeting

Before exporting, choose the date range and zoom so labels and dependency connectors are readable. Include enough context in the project title to identify the reporting date or version. Open the downloaded PDF or PNG and inspect the smallest labels, the final task and the right-hand edge; a successful download does not guarantee the entire timeline is legible.

Split large plans into phases rather than shrinking hundreds of rows onto one page. A management summary needs milestone dates and major blockers, while a delivery-team view can show more detail. PDF and PNG are presentation snapshots, not editable backups of the project data.

Saving and sharing limitations

Local browser storage is tied to the device and browser profile. Opening the app elsewhere does not automatically bring your plan with you, and clearing site data can remove it. Keep the task data in a separate source if you need recovery, and avoid treating an exported picture as your only record.

For timelines embedded inside reporting, see Deneb custom visuals. For reporting that needs shared data, permissions and refresh, see Power BI consulting.

  • No multi-user collaboration — state lives in local storage on one device
  • No resource levelling or critical-path calculation; it is a scheduling picture, not a planning engine
  • Very long projects (300+ tasks) are better split into phases for readability
  • Clearing browser storage clears saved projects, so export before you tidy up