A no-code chart builder if editors and marketers make your charts, and a code library if developers do. Builders let someone paste a spreadsheet and publish from the browser; libraries give a developer full control inside a site or app. Settle who builds the charts first, then compare two tools on your own data.
Datawrapper sells a no-code route from data to chart, and the replacements split on exactly that point. Flourish, Infogram, Vizzlo, Datylon and the recently acquired everviz are browser builders for editors, while Chart.js, Apache ECharts, Highcharts and Plotly are code for developers. That acquisition, by Fonn Group, came with a new product called Teikna, per the vendor's homepage, so check what it's becoming before you build a newsroom workflow on it.
Who builds the chart: nine options compared
| Tool | Who builds it | Free option on its site |
|---|---|---|
| Apache ECharts | Code library | Free and open source |
| Chart.js | Code library | Free and open source |
| Datylon | No-code builder | Not stated |
| everviz | No-code builder | Not stated |
| Flourish | No-code builder | Not stated |
| Highcharts | Code library | Free trial named |
| Infogram | No-code builder | Not stated |
| Plotly | Code library | Free trial named |
| Vizzlo | No-code builder | Not stated |
Editor tool or developer library? Weighing the fork
The two groups solve different problems. A builder puts chart-making in the hands of whoever has the data, which means faster turnaround and less control over the code. A library puts it in the hands of whoever owns the site, which means charts that match your front end and live in your own codebase, but every new chart needs a developer's time.
Questions that settle it quickly:
- Who publishes charts on a deadline, and can they wait for a developer?
- Do charts need to sit inside an app or product, or only in articles and reports?
- Who will keep the house style consistent when several people make charts?
- Where should the chart data live: on a vendor's servers or in your own code?
If you'd like the wider field, including dashboards and BI, my guide to data visualisation tools goes further.
Make a chart builder or charting library that belongs in this comparison? Ask to be considered for a place here.
The nine chart makers by name
Sorted by name and in no particular order beyond that. The use case is my summary; the quoted part is the maker's own claim.
Apache ECharts
Best for: Front-end teams wanting interactive browser charts from an open source library. In the project's words: 'a declarative framework for rapid construction of web-based visualisation'.
Chart.js
Best for: Developers adding simple, flexible charts to a website. In the project's words: 'open source HTML5 charts for your website', maintained by its community.
Datylon
Best for: Report teams whose charts update from Excel, no-code workflows or an API. In the vendor's words: 'design pixel-perfect charts and reusable reports, then automate production'.
everviz
Best for: Broadcast and streaming graphics, the focus the vendor now describes. In its words: 'beautiful interactive visualisations on all platforms'.
Flourish
Best for: Embedding explorable charts, graphs and maps in articles, reports or presentations. In the vendor's words: 'where data meets storytelling'.
Highcharts
Best for: Stock, map and Gantt charts from one JavaScript library family. In the vendor's words, it builds visualisations 'with modern frameworks such as React'.
Infogram
Best for: Marketers making infographics and reports to share or embed. In the vendor's words: 'create interactive data visualisations with AI'.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Plotly
Best for: Python analysts turning charts into interactive data apps with Dash. In the vendor's words, an 'enterprise platform for internal apps and analytics' sits beside its open source libraries.
Vizzlo
Best for: Business charts made inside Google Slides or PowerPoint. In the vendor's words: 'create high-quality charts and business graphics in just seconds'.
Chart advice for newsrooms and marketing teams
If the people making charts are reporters, editors or marketers, stay on the no-code side and judge each builder on how quickly a new starter can publish a correct chart from a pasted spreadsheet. If a developer owns your site's charts, a library fits in with the rest of the code and doesn't need yet another login. Mixed teams can run one of each, as long as you agree who owns the house style.
Whichever side you pick, decide what has to survive the move: embed codes on old articles, colour palettes, fonts, and any charts that update from a live sheet. Old embeds are easy to overlook, so list the pages that carry them before you switch anything off.
Build one chart twice before you choose
Take a chart you've already published and rebuild it from the same data in two tools. Then check each version against this list:
- Phones. Open the embed on a phone and see whether labels, legends and tooltips still read clearly.
- Accessibility. Look for alt text, a data table view or screen reader support, and ask the vendor what it offers.
- Updates. Change one number in the source and time how long it takes to reach the live chart.
- Exports. Try the formats you need for print, slides and social posts.
- House style. See whether your fonts and colours can be saved as a theme so every chart matches.
If your charts mostly live inside reports rather than articles, my Looker Studio alternatives cover reporting tools that pull from live data sources.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Is a charting library harder to use than a chart builder?
For a non-coder, yes. A library needs someone who can write and maintain code, while a chart builder works in the browser. For a developer, a library can be quicker because it fits the site's existing code.
What happens to charts I've already published?
That depends on the tool you're leaving and its terms, so check before you cancel. Make a list of every live embed and decide whether to keep the old account, rebuild the important charts or swap them for static images.
Do I need interactive charts, or will a static image do?
Interactive charts let readers hover, filter and explore, which helps with dense data. A static image is simpler, loads anywhere and is fine for a single clear point. You can use both on the same site.
Which chart types should I test first?
Start with the chart type you publish most often, then add the hardest one you make, such as a map or a chart with many series. A tool that handles both will cope with the rest.
How do I check who owns a charting tool?
Read the vendor's homepage and about page for acquisition news, and look for a recent release or changelog. A product that has changed hands may change direction too.
