Skip to content

Line chart

One value, read as a trend.

Definition · Updated Nov 2, 2026

A line chart joins one value over time, so the eye reads its direction before its numbers. Rises, drops and flat runs show up at once. Use it for latency, prices, sign-ups or any single measure that changes continuously.

Pay once. Every update included.

Live preview

P95 latency, us-eastP95 time to first token in us-east, hourly over the last 24 hours: 1.30 s now, peak 1.45 s, low 0.85 s.1.8 S1.2 S0.6 S000:0006:0012:0018:00NOW
P95 latency, us-east
HourP95
00:000.90 s
01:001.10 s
02:000.95 s
03:001.20 s
04:000.85 s
05:001.00 s
06:001.30 s
07:001.05 s
08:001.15 s
09:000.90 s
10:001.25 s
11:001.40 s
12:001.10 s
13:001.00 s
14:001.35 s
15:001.20 s
16:000.95 s
17:001.10 s
18:001.45 s
19:001.15 s
20:001.05 s
21:001.30 s
22:001.20 s
Now1.30 s

Sample data: P95 latency, us-east, last 24 hours

Size
Data shape
One value per point in time
Good for
Latency, prices, daily counts
Avoid when
Each period is a separate total to compare
Sizes
XS, S, M and L, re-laid out from the data

Anatomy

Inspect it like the Figma file.

The same layers, names and tokens as the component. Select one to read its size, fill and style.

Layers

010 / Line

chart/010-line
plot · line
Layer
area
Type
Vector
Size
724 × 210
Fill
data/primary
Group
Marks · 26

Layers

010 / Line

chart/010-line
plot · line
Layer
area
Type
Vector
Size
243 × 122
Fill
data/primary
Group
Marks · 26

Sizes

Re-laid out, never scaled.

The same data at XS, S, M and L. Every size is redrawn from the data, so text and line weights never shrink.

M against S

Width360 px480 px

Plot328 px440 px

Labels99

Marks2626

Height212 px246 px

Same tokens at every size: text styles, 1 px lines and mark radius stay put.

When to use

One measure, moving.

Three signs it fits, and three signs another type fits better.

Is time on the x axis?

No time, just items side by side.

Yes: Keep the line

Is it one series?

Several series share the axis.

Yes: Keep the line

Is the direction enough on its own?

The amount, not only the trend.

Yes: Keep the line

Code and Figma

One name in Figma and in code.

Every Figma property is a prop with the same name and values. One command installs it.

Figma

chart/010-line

size
legend
Property = propValuesDefault
size"xs" · "s" · "m" · "l""xs"
legendfalsefalse
color"cat-1" · "cat-2" · "cat-3" · "cat-4""cat-1"
npx shadcn add @chartory/line
line.tsx
import { Line } from "@/components/chartory/line"import { p95Latency } from "./p95-latency"export function P95Latency() {  return (    <Line      data={p95Latency}      size="m"      legend={false}    />  )}

Hearth widget

Line as a widget.

The chart in a Hearth card with a hero number and two blocks. One token set, light and dark.

Code
Get the code

EmberPreset

ChartoryDefault preset

Pick the blocks, the size and the preset for your own widget.

Read the Hearth widget docs

FAQ

Line chart questions.

What people ask before they put a line in a dashboard.

Something else?

hello@usechartory.com
  • Use the line when only the direction matters, as with latency. Use an area when the amount under the line matters too, as with a balance or a price.

Related types

The same question, a different shape of answer. Every type ships in Figma and in code.

Same family

Change over time

Trends, levels and seasons across days, months or years.