Scattergl renderer default transition uncertainty after plotly chart_studio split

Answer to the Core Question

Plotly’s core library does not automatically switch a Scatter trace to Scattergl when the point count grows. The renderer is chosen only by the trace type you supply; there is no internal threshold or automatic transition.

In other words:

• To use WebGL you must explicitly create a Scattergl trace (e.g., go.Scattergl in Python or type: 'scattergl' in JavaScript).
• There is no Plotly version that offers a global setting to change the default trace type from SVG to WebGL.
• When a figure is sent to Chart Studio via the chart_studio package, the renderer default of the notebook (e.g., notebook, vscode) does not alter the trace type; Chart Studio stores exactly what you sent.

Why the Confusion Persists

Some community wrappers (e.g., cufflinks, certain Plotly Express helpers) apply heuristics that automatically choose scattergl for large datasets. These are not part of the core Plotly implementation and vary by wrapper version. Relying on them introduces uncertainty because the threshold and behavior are not documented in the official API.

Practical Steps for Large Scatter Plots

1. Choose the right trace type. For datasets larger than a few thousand points, construct the trace as go.Scattergl (Python) or set type: 'scattergl' (JavaScript). Example in Python:

   import plotly.graph_objects as go
   fig = go.Figure(go.Scattergl(x=x_vals, y=y_vals))
   fig.show()

2. Set the renderer for the environment. The plotly.io.renderers.default setting controls where the figure is displayed (browser, notebook, etc.), not the trace type. Example:

   import plotly.io as pio
   pio.renderers.default = 'notebook'  # or 'vscode', 'browser', etc.

3. Publish to Chart Studio. Use chart_studio.plotly.iplot(fig) or fig.show(config={'cloud': True}). The figure will be stored with the same trace type you created. No conversion to SVG will occur.
4. Verify the renderer. In a notebook, inspect the DOM: a <canvas> element indicates scattergl, while a large number of <path> elements indicates SVG.

Version Consistency

Across Plotly 5.15.0 to 5.22.0 (the latest as of 2026‑10‑13), this behavior has remained unchanged. No release notes indicate an automatic transition mechanism.

What to Ask Next

If you are seeing unexpected SVG rendering in a particular environment, confirm whether a community wrapper or custom helper is being used to construct the trace. That could be the source of the automatic switch.

Key Takeaways

• No automatic Scatter → Scattergl transition in core Plotly.
• No global default switch exists; you must set the trace type.
• Chart Studio preserves the trace type exactly.
• Use explicit Scattergl for large point counts to avoid performance issues.