This page is a work in progress. Please bear with us while we're working on this content.
This page will list some conceptual differences between amCharts 4 and 5, which, hopefully, will help you with the decision to upgrade (or not).
Not an upgrade
amCharts 4 and amCharts 5 are conceptually different libraries.
The code between the two is not interchangeable.
In a few words: amCharts 5 was designed to be fast and use less memory footprint than its predecessor.
amCharts 5 uses Canvas API as its method of rendering, whereas amCharts 4 used SVG.
amCharts 5 uses "root element" approach - you create a root element, then add actual chart or series objects to it.
The reference to root element is passed into all chart objects being created.
amCharts 4 did not have a root element, so chart instance was the top element in the tree.
Functional changes in v5
amCharts 4 offered two ways to configure charts: object/procedural and JSON configs.
amCharts 5 offers only object/procedural approach. At this time there are no plans on implementing JSON configs for v5.
There are no 3D-esque chart types in amCharts 5, like 3D columns, pies, or cylinders.
amCharts 5 uses Canvas API, which means it does not use SVG for its rendering.
It also means that exporting chart snapshot to SVG is also not available.
amCharts 5 does not support any version of Internet Explorer, which was supported in amCharts 4.
EDGE browser as well as other modern desktop and mobile browsers are fully supported.
Should I migrate?
- Struggling with performance or memory footprint of amCharts 4.
- Using charts in multi-chart dashboards.
- Need chart types unsupported by v4 like Tree, drillable Suburst, Partition, Pack.
- Need Stock chart type (currently in development for amCharts 5).
- Want charts to be faster and use less memory.
Do not migrate if...
- Still need to support legacy browsers like Internet Explorer.
- Need 3D charts.
- Need to be able to serialize chart configs as JSON.
- Need to generate chart snapshots in SVG format.
- Using amCharts Editor 4.