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.

/
    • Sketches and constraints
    • Features
    • Outputs, regions and published values
    • Configurations
    • Occurrences and mates
    • Patterns, mirrors and fasteners
    • Drawing views and annotations
    • Evaluate
    • Import and export
    • Scripting and sweeps
Docs>CAD>MCAD reference

Import and export

RunMat reads STEP into a part and writes every common mechanical exchange format. Exports come from the editor's Export command, from the agent (design.export) and from the command line (runmat-design export), all through the same writers.

Import

FormatBecomes
STEPan import feature in a part: feature housing = import(source = "supplier/housing.step", digest = …). The body keeps the file's face names, read as feature.housing.face("Top"), and the digest pins the file's content. AP242 semantic PMI comes in as the part's PMI.
KiCad projectscircuits and boards; see Import

Direct edits (direct.move_faces, direct.replace_faces, direct.delete_faces) change an imported body as features in the history, so the supplier's file stays untouched; see Features.

Export

FormatFromCarries
stepa part or an assemblyAP242 geometry, the assembly structure, part numbers (a configured part travels under its own part number), region and output labels as face and product names, and semantic PMI
dxf, dwga drawing, or a sheet-metal part's flat patternsheets with views, annotations and tables
pdfa drawingsheets
3mfa part or an assemblymeshes, for printing
stla part or an assemblya mesh
gltfa part or an assemblymeshes, for viewers and the web
boman assemblythe bill of materials
runmat-design export bracket.part --format step --out exports
runmat-design export bracket.part --format step --all-configurations --out exports
runmat-design export bracket.drawing --format pdf
runmat-design export enclosure.part --format dxf --out flat

Region labels become STEP face names, which is how a study selects them: a region label = "Mounting bores" in the part is select name "Mounting bores" in the .fea file.

Studies of a design

A study reads a part or an assembly's exported STEP today. A .fea geometry that names the design directly, geometry arm { part = arm, inputs = { length = 92 mm } }, regenerates it at the given inputs with no export step Not yet releasedStatus.

On this page
  • Import
  • Export
  • Studies of a design