RunMat
  • Pricing
RunMat
GitHub
GitHub
Sign inTry in browser
DesktopRuntimePhysicsCADAdministrationAgent

Get RunMat updates

New releases, guides and examples.

Product+
  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download
Math+
  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting
Physics+
  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA
Industries+
  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance
Learn+
  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students
Compare+
  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons
Company+
  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms

Product

  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download

Math

  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting

Physics

  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA

Industries

  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance

Learn

  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students

Compare

  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons

Company

  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms
GitHubXLinkedIn

© Dystr, Inc. · RunMat v0.7.1, Nov 17, 2026

RunMat® is a registered trademark of Dystr, Inc. MATLAB® is a registered trademark of The MathWorks, Inc. RunMat is not affiliated with, endorsed by, or sponsored by The MathWorks, Inc.

/
    • Plotting System
    • Figure State & Handles
    • Rendering Pipeline
    • Replay & Export
    • Host Integration
Docs>Runtime>Plotting

Replay & Export

Replay and export both start from a figure.

Replay preserves a live graphics scene: plot objects, axes metadata, subplot layout, legends, labels, limits, color settings, view-related state, and enough plot data to reconstruct a Figure.

Export preserves pixels: one rendered observation of that scene at a particular size, theme, and camera state.

Scene Versus Image

Loading diagram...

A replayed figure remains editable and renderable. An exported image is a fixed artifact. Replay preserves each axes and its state. Export preserves the composed pixels from the current observation.

Replay Payload

export_figure_scene captures a cloned figure as FigureScene and wraps it in a runtime replay envelope. The envelope stores schema version, payload kind, creation time, and the scene itself.

Loading diagram...

Import reverses the process. The runtime decodes the envelope, validates schema and limits, hydrates any large-data references, converts the FigureScene back into a Figure, registers it in the plot registry, and returns a fresh figure handle.

What Replay Preserves

Replay preserves interpreted graphics state. The preserved state includes:

  • subplot grid and axes membership
  • active axes selection
  • plot objects and plot-specific style/data
  • axes titles, labels, legends, limits, scales, grids, boxes, colorbars, colormaps, and color limits
  • figure background and super-title
  • visibility, labels, text annotations, and 3-D view metadata

The original script may have created that state. Replay reconstructs the figure directly from serialized scene state.

Schema And Limits

There are two schema boundaries:

BoundaryPurpose
Runtime replay envelopeRejects wrong payload kinds, unsupported envelope versions, oversized payloads, and excessive plot counts.
FigureScene schemaVersions the renderable figure representation and rejects scene content that cannot be reconstructed safely.

Default scene replay limits are:

LimitDefault
Encoded figure scene payload16 * 1024 * 1024 bytes
Plot count4096 plots

Large scenes can reference external array payloads. The import path can hydrate supported surface and 3-D scatter fields from dataset manifests or chunk references before reconstructing the figure.

Scene version 6 preserves the exact IEEE-754 bits of nonfinite single- and double-precision plot source values in JSON. Finite values retain their ordinary numeric representation. Older finite scenes remain readable, but an older reader cannot open a version 6 scene. A legacy typed source containing JSON null is rejected because the original NaN or infinity value cannot be recovered from it.

Export Path

Export renders a figure through the headless image exporter. The runtime can render PNG bytes or raw RGBA bytes, with default camera state, one explicit camera, or per-axes cameras.

Loading diagram...

Snapshot helpers clone the figure by handle, apply dimensions, set the active plot theme, optionally attach a textmark, and render. Camera-aware snapshot helpers convert host-facing camera state into runmat-plot camera values before export so the image can match the interactive view.

Choosing The Right Operation

NeedUse
Restore a figure later as editable graphics state.Replay scene export/import.
Preserve the current view for a report or preview.PNG or RGBA export.
Keep subplot structure and per-axes state.Replay.
Match the user's current interactive 3-D view in an image.Camera-aware export.
Share a fixed artifact that no longer needs handles or axes state.Image export.

Replay keeps the scene alive. Export records what the scene looked like at one moment.

On this page
  • Scene Versus Image
  • Replay Payload
  • What Replay Preserves
  • Schema And Limits
  • Export Path
  • Choosing The Right Operation