Does the Gantt maker change my task dates automatically?

Manual mode preserves entered start/end ranges and validates dependency order. For start plus duration, it calculates an inclusive end date using configured working weekdays. The separate finish-to-start scheduling mode explicitly moves starts forward to a working date after every predecessor ends. Requested inputs remain unchanged and visible beside planned dates. Baselines never move unless you edit or capture them.

How do weekends and working-day durations work?

Choose the weekdays that are nonworking. A two-working-day task beginning Friday finishes Monday when Saturday and Sunday are nonworking, or Saturday when every day is working. No holidays are inferred. All seven days nonworking produces an actionable error. Date-only calendar arithmetic avoids local timezone and daylight-saving shifts.

What dependencies are supported?

Enter stable task IDs such as T1, T2 as finish-to-start predecessors. A successor must start on a later working date than its latest predecessor finish. Missing task IDs, duplicate references and dependency cycles are rejected. Removing a task keeps any remaining references visible for explicit correction. Other dependency types, lag, critical-path analysis and automatic resource scheduling are not included.

How are progress, resource labels and baseline shown?

Progress is the supplied percentage from 0 to 100 and fills that fraction of the calendar-span bar. Resource labels are descriptive, with no automatic assignments or conflict resolution. Baseline start/end dates appear as amber bars and can be entered independently or captured from the current displayed plan. The complete task table and exports preserve every field.

Can I export and reopen the complete plan?

SVG contains every task bar, progress, baseline and full task details. CSV contains all input fields, calculated dates and repeated plan settings, with spreadsheet formula guards. The CSV importer accepts this tool's complete exported format and validates calculated dates against inputs. Project JSON preserves exact editable data and imports transactionally. Valid touched plans also save locally in this browser.

Will the PDF include all tasks and long names?

PDF uses A4 landscape pages with up to 18 task bars per timeline page, followed by complete flowing task details. Labels on the timeline use stable task IDs; the details preserve full names, resources, requested dates, calculated dates, progress, dependencies and baseline. Text is drawn into page images using browser fonts so Unicode is retained, rather than embedded as selectable PDF text. Long timeline ranges can contain subpixel short bars, so exact task dates are always included in the details.

What are the working limits?

A local project supports 100 tasks, 20 predecessors per task, 1 to 366 working days per task, and dates from 1900 through 2100. Tasks and baseline together must fit a 3,650-calendar-day timeline. Names, resource labels and the plan title each support 120 characters. PDF preparation can be canceled and stops after 60 seconds or 200 pages without downloading a partial file. Processing stays in the browser.

Gantt Chart Maker

Enter task rows and choose whether to validate manual dates or explicitly schedule finish-to-start dependencies. Keep requested dates visible beside the calculated timeline, configure nonworking weekdays, edit progress and resource labels, and capture or edit a fixed baseline. Export the complete plan as SVG, CSV, paged PDF or editable project JSON.

Plan and working calendar

Plan titleDate policy

Manual mode keeps entered date ranges and validates predecessor finishes. Duration mode calculates an inclusive end using configured working weekdays. Scheduling explicitly moves starts forward to a working day after all predecessors, preserves working-day duration and keeps requested inputs unchanged. No resources are automatically assigned.

Nonworking weekdays

Weekdays only; no holidays are inferred. Dates use a calendar-day axis and inclusive ends. Progress fills the same percentage of the displayed bar; it is supplied progress, not elapsed working time.

Baseline dates stay fixed until explicitly edited or captured again. Scheduling never changes them.

Editable task rows

Add a task to start. Input and result dates will remain visible together after validation.

Current timeline

Draft preview; build after your changes. Teal bars show planned calendar-date spans, dark teal shows supplied progress, amber shows baseline. Click a task row or use its focused row button to select it. The full data table below includes every name, resource, predecessor and date. Long timelines can contain subpixel short bars; read exact dates in the table.

Add valid task rows or correct the current validation message to preview the complete timeline.

Complete task data

0 total tasks. Requested dates remain unchanged by scheduling. Select any row to edit its full data.

Task / resource	Requested input	Planned dates	Dependencies / progress	Baseline

Page 1 of 1

Add your tasks, choose the date policy and build the complete timeline.

Validated tasks: Pending

Calendar span: Pending

Baseline tasks: Pending

Predecessor links: Pending

Import project JSONImport Gantt CSV

CSV contains every input plus calculated dates and repeated plan settings, with spreadsheet formula guards. Import accepts this complete exported format and checks its calculated dates. JSON preserves exact editable data. PDF uses A4 landscape pages with up to 18 task bars per timeline page and complete flowing task details afterward. PDF text is rendered as images to retain browser Unicode glyphs; it is not selectable text.

Local bounds: 100 tasks, 20 predecessors per task, 1 to 366 working days per task, dates from 1900 through 2100, and a full timeline including baseline of at most 3,650 calendar days. PDF stops after 60 seconds or 200 pages without downloading a partial file. Names and resources support 120 characters each.

Accuracy. A plan from user assumptions; no promised completion forecast or automatic staffing decisions.

Common questions

Does the Gantt maker change my task dates automatically?: Manual mode preserves entered start/end ranges and validates dependency order. For start plus duration, it calculates an inclusive end date using configured working weekdays. The separate finish-to-start scheduling mode explicitly moves starts forward to a working date after every predecessor ends. Requested inputs remain unchanged and visible beside planned dates. Baselines never move unless you edit or capture them.
How do weekends and working-day durations work?: Choose the weekdays that are nonworking. A two-working-day task beginning Friday finishes Monday when Saturday and Sunday are nonworking, or Saturday when every day is working. No holidays are inferred. All seven days nonworking produces an actionable error. Date-only calendar arithmetic avoids local timezone and daylight-saving shifts.
What dependencies are supported?: Enter stable task IDs such as T1, T2 as finish-to-start predecessors. A successor must start on a later working date than its latest predecessor finish. Missing task IDs, duplicate references and dependency cycles are rejected. Removing a task keeps any remaining references visible for explicit correction. Other dependency types, lag, critical-path analysis and automatic resource scheduling are not included.
How are progress, resource labels and baseline shown?: Progress is the supplied percentage from 0 to 100 and fills that fraction of the calendar-span bar. Resource labels are descriptive, with no automatic assignments or conflict resolution. Baseline start/end dates appear as amber bars and can be entered independently or captured from the current displayed plan. The complete task table and exports preserve every field.
Can I export and reopen the complete plan?: SVG contains every task bar, progress, baseline and full task details. CSV contains all input fields, calculated dates and repeated plan settings, with spreadsheet formula guards. The CSV importer accepts this tool's complete exported format and validates calculated dates against inputs. Project JSON preserves exact editable data and imports transactionally. Valid touched plans also save locally in this browser.
Will the PDF include all tasks and long names?: PDF uses A4 landscape pages with up to 18 task bars per timeline page, followed by complete flowing task details. Labels on the timeline use stable task IDs; the details preserve full names, resources, requested dates, calculated dates, progress, dependencies and baseline. Text is drawn into page images using browser fonts so Unicode is retained, rather than embedded as selectable PDF text. Long timeline ranges can contain subpixel short bars, so exact task dates are always included in the details.
What are the working limits?: A local project supports 100 tasks, 20 predecessors per task, 1 to 366 working days per task, and dates from 1900 through 2100. Tasks and baseline together must fit a 3,650-calendar-day timeline. Names, resource labels and the plan title each support 120 characters. PDF preparation can be canceled and stops after 60 seconds or 200 pages without downloading a partial file. Processing stays in the browser.

A plan from user assumptions; no promised completion forecast or automatic staffing decisions.