Smartsheet makes its Gantt view available once a sheet contains Date-typed Start Date and End Date columns, an optional Duration column, and a Percent Complete column; after those columns exist, the toolbar's Gantt view toggle draws horizontal task bars against a configurable timescale that Project Settings controls. The same kind of dated project timeline can also be produced in a single browser tab using Gantt Chart Maker, which converts 2 to 30 task,start,end rows into a deterministic UTC timeline and downloads the exact preview as a standalone SVG file. The Smartsheet route requires an active workspace, the four-column setup, and a separate configuration pass for primary and secondary headings, working days, dependencies, and baseline columns. The browser route needs only the schedule rows themselves, an optional title, and a generate click. Readers who arrived searching for the Smartsheet workflow get the column-first steps in the next sections, followed by a parallel browser path that produces a comparable dated timeline from a much smaller input.
Smartsheet's Gantt View and What It Expects
Smartsheet's Gantt view is a sheet-level presentation, not a separate chart type. The view reuses the rows already entered and depends on four columns being present and well-typed. Start Date and End Date must be Date-type columns so Smartsheet can place a bar across a span. Duration is optional and lets Smartsheet auto-compute end dates from start dates plus an effort estimate. Percent Complete accepts 0 to 100 percent values that shade each bar to indicate progress. When those four columns exist and the sheet has been switched to Gantt view, the bars appear automatically; without the columns, the Gantt view option either stays disabled or renders empty bars that show no schedule.
Project Settings is where the view's appearance and behavior are tuned. From there you can adjust the Primary and Secondary headings that label the timescale, narrow the chart to specific working days, set up predecessor links for dependencies, and add a baseline column for variance reporting. None of those settings are required to make the Gantt view draw, but they decide whether the chart conveys useful project-management signal once it appears.
Setting Up a Gantt Chart in Smartsheet Step by Step
The native Smartsheet workflow runs in column-first order, with each step unlocking the next.
- Add a Date-typed Start Date column and enter a real calendar date for every row that should appear as a task.
- Add a Date-typed End Date column and enter a date on or after each row's Start Date; Smartsheet will not draw a bar if End Date precedes Start Date.
- Add an optional Duration column if you want Smartsheet to back-calculate End Date from Start Date plus a time estimate; leave Duration blank if you prefer to set both dates yourself.
- Add a Percent Complete column as a 0 to 100 number column so the bars can shade by progress.
- Select Gantt view from the view bar at the top of the sheet; the toggle only becomes available once the four columns exist.
- Open Project Settings from the right-hand panel to configure Primary and Secondary headings (day, week, month, quarter, year), restrict the timescale to particular working days, and turn on dependencies if predecessors matter.
- Add a Baseline Start and Baseline End column pair if you want the original plan to remain visible alongside the current schedule.
- Confirm each bar's left edge lines up with its Start Date and its right edge lines up with its End Date before sharing the view with collaborators.
That sequence mirrors the order Smartsheet's own setup guide describes, where Project Settings becomes the configuration step that turns a default Gantt view into a tuned project chart.
Where a Browser Timeline Pulls Ahead
The Smartsheet route gives you collaboration, permissions, dependencies, baselines, and sharing controls — none of which a browser-side timeline is trying to replace. For a quick dated timeline of a small schedule, the browser path avoids the cost of those features. There is no workspace to create, no view type to switch, no Percent Complete column to add, and no Project Settings pass to navigate. The input is the schedule itself, formatted as one task per non-empty row. The output is a standalone SVG that can be downloaded, embedded in a slide deck, attached to an email, or pasted into a document. Nothing leaves the current browser tab, so the data stays on the device used to type it.
The Gantt Chart Maker route also keeps the schedule deterministic. The chart is computed from the rows as written, with no clock, no locale, and no timezone influence on the bar positions. Two users who paste the same rows on different days, in different timezones, on different operating systems get the same SVG. That determinism is what makes the downloaded file a reliable artifact rather than a one-time snapshot.
Building the Same Timeline in Gantt Chart Maker
The browser path runs in input-first order: rows in, preview out, SVG downloaded.
- Open Gantt Chart Maker and optionally type a title of up to 100 code units into the title field.
- Paste 2 to 30 non-empty rows into the schedule field, with each row in task,start,end form and exactly two commas separating the three fields.
- Write each date as a real UTC calendar date in exact YYYY-MM-DD form, with four-digit year, hyphen, two-digit month, hyphen, two-digit day.
- Make sure each end date sits on or after its start date; end dates are inclusive, so a task from 2025-01-01 to 2025-01-03 occupies three day cells (3 minus 1 plus 1 equals 3), and a same-day row occupies one cell.
- Click Generate; the parser checks the raw input budget of 20,000 code units, then validates every row, then renders the preview against a deterministic UTC axis.
- Inspect the preview and verify every bar and tick matches your input; one malformed row rejects the entire request rather than producing a partial chart.
- Click Download to save the standalone SVG; the file is built from the same string the preview rendered, with the W3C SVG 2 namespace, a viewBox, an accessible role and label, and user strings converted to XML entities.
How the Preview Becomes the SVG Download
The exact SVG markup used to draw the visible preview is also the markup that gets downloaded. That means every coordinate, label, and tooltip on screen is reproduced verbatim in the saved file. The chart uses the W3C SVG namespace at a fixed 1,100-pixel logical width with a row-dependent height, a white background, grid lines, labeled bars, title tooltips, and a viewBox so the file scales cleanly when opened in a browser, a slide deck, or a vector editor.
The horizontal domain begins at the earliest task start and ends after the latest inclusive task day. Each day's width is the plot width divided by the inclusive day count, so positions round-trip deterministically and the chart never inherits locale, current date, daylight-saving, or timezone quirks from the device. Tick sampling is deliberate: spans of 62 days or fewer use deterministic day ticks in YYYY-MM-DD form, and longer schedules switch to bounded month-step ticks in YYYY-MM form so the axis never has to render thousands of labels. All tasks remain present in the chart regardless of which tick mode is active.
User-supplied strings are never embedded as markup. Ampersands, angle brackets, quotes, and apostrophes are converted to XML entities before they reach the SVG, and XML-forbidden control characters and isolated surrogates are replaced with U+FFFD so a label that looks like a script tag stays visible as text. The combined SVG output is checked against an explicit 100,000-code-unit budget; one unit over that budget causes the request to fail rather than truncate the chart.
Validation Rules That Reject a Schedule
Gantt Chart Maker is strict on purpose: one malformed row rejects the entire request rather than producing a partial chart that misrepresents the schedule. The table below lists the rules that decide whether a request generates successfully.
| Field | Rule |
|---|---|
| Rows | 2 to 30 non-empty rows, one per task |
| Row format | Exactly two literal commas per non-empty row, leaving three fields: task,start,end |
| Date format | YYYY-MM-DD, real proleptic Gregorian UTC date |
| Year range | 0000 through 9999 |
| End date | Inclusive, on or after the start date |
| Label length | Up to 80 UTF-16 code units per task label |
| Title length | Up to 100 UTF-16 code units |
| Raw input | Up to 20,000 code units before blank-line trimming |
| SVG output | Up to 100,000 code units total |
| Tick mode | Day ticks for spans of 62 days or fewer; month-step ticks for longer spans |
The CSV-lite format intentionally rejects commas inside labels, quoted fields, escaped delimiters, and additional columns. A label that needs a comma must be rewritten without one. The parser does not infer whether overlapping work is feasible, infer dependencies, infer milestones, or claim a schedule is realistic; those belong to a full project-management tool. For Smartsheet readers specifically, the browser path is a quick visualization companion rather than a replacement for the dependency, baseline, and collaboration features that the native Gantt view provides.