naver/billboard.js: A D3-Based Chart Library with SVG and Canvas Rendering
📊 Re-usable, easy interface JavaScript chart library based on D3.js, with SVG and Canvas rendering support
At a glance
- What is it?
- billboard.js is a TypeScript chart library built on D3.js that offers both SVG and an opt-in Canvas rendering mode. It suits teams that want a D3 foundation without writing D3 directly, and it is the wrong tool if you want a framework-native component tree.
- Who is it for?
- Adopt billboard.js if you want a D3-based charting layer with a documented option object, and if you need SVG output with an opt-in Canvas path for dense axis charts. Do not adopt it if you expect a framework-native component model; the repository also exports a React entry point, but the primary interface is an imperative option object.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- naver/billboard.js6,028 ★ · +17
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| naver/billboard.js | 6k | 6k |
17 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What billboard.js solves, and who it is for
D3.js gives you primitives: selections, scales, axes, transitions. Assembling those into a chart that behaves predictably across chart types is repetitive work, and each team that does it invents its own conventions. billboard.js sits on top of D3 and exposes a single option object instead of a chain of selections. The README describes it as a "re-usable, easy interface JavaScript chart library based on D3.js", and the name is a nod to the Billboard chart.
The audience is engineers who already accept D3 as the rendering foundation but do not want to hand-write axis ticks, tooltip positioning and legend toggling for every chart. The repository is TypeScript, and package.json ships a types entry, so TypeScript consumers get declarations from the package rather than from DefinitelyTyped. If your team has standardized on a component framework and expects charts to be declared as components with props and lifecycle hooks, this is a different model. The library is imperative at its core: you hand it a container element and a configuration object.
How the option object maps onto D3
The public surface is a constructor plus a configuration object. You give billboard.js a bind target and describe data, axis, type and interaction in one place. The result is rendered as SVG by default.
v4 adds a second rendering path. The README notes that "v4 adds an opt-in canvas rendering mode for high-density axis charts" and directs readers to the Canvas rendering mode section of CHANGELOG-v4.md for supported chart types, ESM import usage, interactions and SVG parity scope. That last phrase matters. Canvas rendering is opt-in and scoped, not a drop-in replacement for the SVG path across every chart type. The package exports a separate entry point for it: package.json maps "./canvas" to dist-esm/index.canvas.js for import and dist/billboard.pkgd.js for require, with types at types/canvas.d.ts. There is also a "./react" entry point with its own types directory, so React consumers have a documented subpath rather than an unofficial wrapper.
Installing billboard.js and drawing a first chart
The README says to download dist files from the repo directly or install it with pnpm. It gives this command for installing from the nightly branch:
pnpm add git+https://github.com/naver/billboard.js.git#nightlyThat line is for the nightly build, which the README describes as the latest build from the master branch and which carries a version string of the form x.x.x-nightly-yyyymmddhhmmss. For a normal install the README says the library is installed with pnpm, and it lists direct dist URLs under naver.github.io with separate uncompressed files for development and minified files for production. The packaged build that bundles D3 is explicitly flagged as not an official distribution, so treat it as a convenience rather than the default. A theme is applied by loading one of the theme CSS files in place of the default stylesheet; the README lists datalab, dark, insight, graph and modern, each with a plain and a minified variant.
A first chart needs a container element and a configuration object. The demo directory in the repository contains demo/chart.js and demo/index.html, and the API documentation is published at naver.github.io/billboard.js/release/latest/doc/. The configuration keys are documented there rather than in the README, so read the API page before writing your first option object. For the Canvas path, the README points to the ESM import usage notes in CHANGELOG-v4.md rather than to the root entry point, so read that section before switching imports.
Where billboard.js is the wrong choice
The Canvas mode is the clearest boundary. It is opt-in, it is documented as covering high-density axis charts, and the README defers its interactions and SVG parity scope to a changelog section. If your application relies on SVG-specific behaviour such as DOM inspection in tests, CSS selectors reaching individual chart elements, or accessibility tooling that walks the SVG tree, switching a chart to Canvas changes those assumptions. The README does not claim full parity; it tells you to read the scope notes.
The second boundary is the interface model. billboard.js is not a declarative component library. State changes go through the chart instance, and the container element is a plain DOM node. In a framework with a strict render pipeline, you are responsible for creating the chart after mount and destroying it before unmount; nothing in the option object manages that lifecycle for you. The repository does expose a "./react" subpath with its own types, so React users have a supported entry point, and the README's React section describes the component.
A third constraint is documentation shape. The README is a hub of links: API documentation, examples, roadmap, comparison table, migration guide, benchmark, wiki pages. That is a lot of surface, and the answers to specific questions often live in the wiki rather than in the README itself.
billboard.js compared with Chart.js and other charting libraries
The difference between billboard.js and Chart.js is architectural rather than cosmetic. Chart.js is a self-contained charting library with its own rendering pipeline and its own configuration model; you do not need D3 to use it. billboard.js is explicitly built on D3, and the README states that directly. If your team already uses D3 for other visualizations, billboard.js keeps one rendering foundation under the whole page. If you have no D3 dependency and no intention of adding one, Chart.js avoids that layer entirely.
The other axis is rendering. Chart.js renders to Canvas by default. billboard.js renders to SVG by default and added Canvas as an opt-in mode in v4. That ordering matters for the kind of work you do: SVG output is easier to inspect and style with CSS, while Canvas tends to be the choice when the number of plotted points makes DOM node count the bottleneck. The repository ships a PERFORMANCE.md file and a demo/benchmark directory, so the project tracks this question itself rather than leaving it to blog posts.
There is also a migration path worth knowing about. The README links a migration guide from C3.js, which is the strongest signal of where billboard.js expects part of its audience to come from. If you are maintaining a C3-based dashboard, that guide is the first document to read, not the API reference.
Maintenance, releases and the MIT licence
The repository is not archived, and the last push was on 2026-10-27. Releases are managed through semantic-release, which the README advertises with a badge and which the .releaserc.json file in the repository root confirms. The release list shows 4.1.3 on 2026-10-16, preceded by 4.1.2 on 2026-10-15 and 4.1.1 on 2026-09-30.
Upgrade cost is the part that needs attention before you commit. The README links separate changelogs for v2, v4 and the general CHANGELOG.md, plus migration guides for v2 and for C3.js. A library that carries per-major migration documents is telling you that major upgrades are not silent. Plan for reading the v4 changelog, particularly the Canvas rendering mode section, if you adopt the Canvas path, because its supported chart types and interaction scope are defined there.
The licence is MIT, which is permissive and imposes no source-disclosure requirement on your application. Note only that the packaged build bundling D3 is described as not an official distribution; if you use it, you are relying on a convenience artifact rather than the supported one. This is a description of the licence and packaging facts, not legal advice; your own counsel should review anything you ship.
Editorial conclusion
Adopt billboard.js if you want a D3-based charting layer with a documented option object, and if you need SVG output with an opt-in Canvas path for dense axis charts. Do not adopt it if you expect a framework-native component model; the repository also exports a React entry point, but the primary interface is an imperative option object. Before committing, verify the Canvas parity scope in CHANGELOG-v4.md, confirm the package manager your project uses against the install command in the README, and check the migration guide if you are coming from C3.js.
Frequently asked questions
How do I install billboard.js?
The README says to download dist files from the repo directly or install it with pnpm. Uncompressed and minified dist files are also published under naver.github.io for the latest release and for specific versions.
Does billboard.js support Canvas rendering?
Yes, v4 adds an opt-in canvas rendering mode for high-density axis charts. The README directs readers to the Canvas rendering mode section of CHANGELOG-v4.md for supported chart types, ESM import usage, interactions and SVG parity scope.
How to chart in billboard.js?
You generate a chart by passing a configuration object to the library, and the repository's demo directory contains demo/chart.js as a working reference. The API documentation is published at naver.github.io/billboard.js/release/latest/doc/.
Can I use billboard.js with React?
The package.json exports a "./react" subpath pointing to dist-esm/react/index.js for import, with types at types/react/index.d.ts. The README has a React section describing the component.
What licence does billboard.js use?
The repository licence is MIT. The README also notes that the packaged build which includes D3 is not an official distribution.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/naver-billboard-js)Star history chart for your README
[](https://hysenlabs.com/projects/naver-billboard-js)Was this useful?