Online Gantt Chart Maker: tips and common mistakes

What Online Gantt Chart Maker actually does

It's a browser-based timeline builder that turns a pasted list of tasks and dates into a rendered Gantt chart, usually in under a minute. There is no account, no upload step and no spreadsheet to format first — the chart redraws on every keystroke, so you can watch the timeline settle as you type.

The input is deliberately plain text. One task per line in the form `Task name, start date, end date`, with an optional fourth value for progress from 0 to 100. Blank lines are skipped, and commas, tabs or pipe characters all work as separators, which matters when you're pasting straight out of a ticket tracker or a notes app.

The output is a live canvas preview with a date scale header, one row per task, a bar spanning its dates, optional progress fill, dependency arrows and a today marker line. From there you export a shareable PNG, a CSV you can reopen in Excel or Sheets, or an ICS file for Google Calendar and Apple Calendar. It sits alongside the rest of the free online tools on OnlineFree.app, which run in the browser with nothing to install.

Formatting rules that stop parse errors

Most unusable pastes come down to a single line the parser cannot resolve into a valid date pair. The tool flags those lines instead of guessing, but it is quicker to get the shape right the first time.

Stick to `YYYY-MM-DD`. `MM/DD/YYYY` is also accepted, which means 03/04/2025 is read as 4 March 2025 — fine for US teams, a silent trap everywhere that writes dates day-first. ISO 8601 order (ISO 8601) removes the ambiguity and sorts correctly when you open the exported CSV later. Don't mix formats inside one paste; that is the fastest route to bars running in the wrong direction.

The subtler trap is a comma inside a task name. Because comma is a valid separator, `Design, review mockups, 2025-01-06, 2025-01-10` can be read as a task called "Design" with the wrong dates attached. Switch that file to pipe or tab separators, or drop the comma from the name. Keep names short too — long names squeeze the bar area on the canvas.

How should you write dependency arrows?

Each dependency line takes the form `Prerequisite -> Dependent`, matched against the task names in your list by exact text. The tool draws a finish-to-start arrow, so the dependent bar starts where the prerequisite bar ends.

Name mismatch is the usual culprit when an arrow refuses to appear. `QA pass` and `QA Pass` are two different tasks as far as the matcher is concerned, and spaces around the arrow are tolerated but a stray trailing space in a task name is not. If you rename a task later, every arrow that pointed at the old name orphans itself without a warning — re-check the dependency block after any rename.

The arrows are communication, not scheduling logic. Nothing is recomputed: push a start date out by three days and the dependents stay exactly where they were until you edit them. That's a deliberate simplification, since real constraint solving belongs in a dedicated project suite. Before sharing the chart, glance at the today marker line and ask whether the bars on the right of it still match what the team believes.

Progress percentages: where teams go wrong

The optional fourth value on a line is progress from 0 to 100, drawn as a fill inside the bar. `Frontend build, 2025-01-11, 2025-01-20, 60` renders a bar that is 60 percent filled. Keep values inside 0-100 and keep them whole numbers; the fill is a visual cue, not a computed metric.

Two habits cause most of the arguments. The first is rounding to 100 while a review, handover or sign-off is still outstanding — a fully filled bar reads as "done, stop asking" to everyone except the person who still has work to do. The second is tracking progress on tasks with no dates yet, which gives you a percentage with no row to live in.

If the chart feeds a client update or an invoice, treat the percentages as self-reported and verify anything financially significant against your own records. The tool renders exactly what you type; it cannot know whether 60 percent is honest.

Choosing between PNG, CSV and ICS exports

Pick the format by who needs to see it next. The PNG is rendered at 2x device pixel ratio through canvas.toBlob(), with a title and a generated-on date footer, saved as gantt-chart-YYYY-MM-DD.png. That makes it crisp enough for a slide deck, a status email or a client PDF, and the dated filename tells you at a glance how stale an image is.

CSV gives you the columns Task, Start, End, Duration (days), Progress % and Depends On, written with a UTF-8 BOM so Excel opens accented characters cleanly instead of mangling them. Check the Duration column before the file goes to finance: a task running 2025-01-06 to 2025-01-10 covers five calendar days, and you want to confirm your first row matches the convention your team uses.

ICS creates one all-day VEVENT per task for import into Google Calendar or Apple Calendar. Per RFC 5545, DTEND is exclusive for all-day events, so the exported end date lands one day after the end date you typed — that is correct behaviour, not an off-by-one bug, and it is what makes the calendar entry cover the final day rather than stopping the night before. Import one task first and confirm it looks right before trusting a whole schedule.

When a simple Gantt chart is the wrong answer

Be clear about the limits. There is no resource leveling, no critical path calculation, no cost column, no shared editing and no version history. Because the tool has no backend, nothing persists between visits — reload the tab and your task list is gone. Export or copy the text out before you close it.

Where it earns its place is 5-40 task timelines: a website build, a course module, a hiring plan, a launch checklist. That is the range where you need something presentable in two minutes and a spreadsheet would cost you twenty. Beyond a few hundred lines the chart becomes a wall of unreadable rows, and shared editing or auto-scheduling needs a proper project suite.

If what you are actually planning is a knockout schedule rather than a project, the Tournament Bracket Maker is the better fit — different shape entirely. For anything the timeline feeds into, such as a contract, grant report or invoice, cross-check the exported dates against your source of truth before sending. The Online Gantt Chart Maker is precise about what you typed; it can't know what you meant.

References

• RFC 5545 — Internet Calendaring and Scheduling Core Object Specification (iCalendar)
• ISO 8601 — Date and time format