

Welcome to the live demo page. These demos are best viewed on a desktop. They run on mobile too, reduced in complexity, so you can still compare them there.
Each opens in a new window. No install, no account, no email, no licence key.
A single line chart carrying five subsets of up to twenty million points each — one hundred million points in the browser. That is not a reduced web figure: it is the size our Win32 desktop demo runs, and the demo labels it so.
The whole dataset is replaced on every tick, not appended to. Turn the timer on and the engine re-passes all five subsets each frame. Replacement is the case most web charts quietly avoid demonstrating, and it is the one the engine was built for.
It starts at 400,000 points so the page is usable immediately, and the ladder goes up from there. You can combine or separate the Y axes, highlight one subset at a time, hide the axes, cap the zoom and watch the frame rate while you do it.
On a phone the three largest sizes are removed from the list rather than offered and allowed to fail. A hundred million points needs roughly 458 MB, and a phone browser ends that tab without warning.
Three chart types on one screen, driven by one dataset. A lit 3D surface, a 2D contour of the same data, and a 2D line through the slice you select. Move the slice and all three follow.
The surfaces are real scanned data, not generated noise: the Grand Canyon at 1345 x 1345, material surface scans at 1232 x 1028 and 1256 x 684, and a noisy terrain at 1451 x 1451. Rotate it, magnify it, explode the Z axis, and move the light around the model.
Rendering is WebGPU, so the surface is drawn by the same graphics hardware a native application would use.
WebGPU needs a current browser and a secure context. If the 3D view does not appear, that is almost always the browser rather than the machine.
The same example set that ships with our desktop demo — the one WinForms, WPF, WinUI, MFC and Delphi developers have been reading for thirty years — running natively in your browser on WebAssembly.
The list is on the left, the JavaScript source is in the top-right pane, and the chart is below it. Click an example and you are looking at working code and the chart it produces, side by side.
Most charting demos show a finished picture and hide the code behind a "view source" link or a documentation page written months apart from the example. Ours puts the JavaScript that produced the chart directly above the chart, in the same window, always in sync — because it is the file the demo just executed.
The question an engineer is really asking is not "can it draw this?" but "how much code is this going to cost me?" Reading the property list beside the result answers that in about five seconds, and it is the honest way to be judged.
It is also the same code you would write on the desktop. The JavaScript property names are the WinForms property names, so a C# developer reading these examples is reading a language they already know. See the walkthrough for the side by side.
Grouped by control type, the way the demo groups them.
Bars, lines, areas, splines and stacked plots, with the axis, legend, annotation and table machinery a production chart actually needs.
The scientific graph: multiple and overlapped axes, log-log scaling, double-precision data, millisecond date-time, contours, heatmaps, spectrograms and Delaunay meshes.
The three real-time shapes: append and autoscale, append against a pinned axis, and overwrite-in-place with a moving write head. Plus the full-replacement case, where every point is new on every frame.
Polar, bi-polar, rose and Smith charts - the RF and antenna work most JavaScript libraries do not attempt at all.
Exploded slices, optional legends and hatching.