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.

/
    • Work together live
    • Work offline and recover edits
    • Work with large projects and data
Docs>Desktop>Work together

Work with large projects and data

A cloud project can hold far more data than fits on a laptop. Desktop keeps only the part of a project you are using on your device, and brings the rest from the server when your code or editor asks for it. Your own edits stay on the device until the server has them.

Where project data lives

TierWhat it holdsSizeLifetime
MemoryRecent file reads and folder listings for the open projectUp to 256 file reads and 256 folder listings per filesystem clientThe session; cleared when the file changes
Disk cacheFiles you have opened or your code has read, as downloaded copies10 GiB of file content per projectKept across sessions, cleaned up in least-recently-used order
ServerEvery file, every saved version and every dataset chunk in the projectNo per-project size limit in DesktopKept with the project and its history

The installed app keeps its disk cache on your computer. In the browser, the same app uses browser-managed storage for editor recovery and short-lived caches, and reads other content from the server each session. Local folder projects don't use these caches: their files are the files on your disk.

Large datasets load in pieces

Store large arrays as datasets rather than single files. A dataset is split into chunks, and reading a slice downloads only the chunks that slice touches. A script that reads one day of sensor data from a multi-terabyte dataset transfers that day's chunks, not the dataset. Writes go to the chunks they change. This is how a project can reach terabytes or petabytes of data while a run on a laptop stays fast.

Set the chunk shape to match how the code reads the data; see Choosing chunks.

How the disk cache cleans up

When the downloaded content for a project passes 10 GiB, Desktop removes the least recently used clean files until the cache is back to 8 GiB. A clean file is one whose content matches the server.

Cleanup never removes:

  • files with edits that haven't reached the server;
  • files with pending moves, renames or deletes;
  • the project's file tree and file details, so a removed file still shows in the tree and downloads again when opened.

Removing a cached copy doesn't touch the file on the server or its history. Package storage and saved run artifacts are managed separately and don't count toward the 10 GiB.

Shared-editor recovery copies have their own cleanup: copies of closed documents whose edits have reached the server are removed after seven days, or sooner to stay within 128 MiB per account. Pending edits, review proposals and documents open in any window are kept.

Change the cache size or location

Not yet releasedStatus Settings › Storage sets the disk cache size per project and for the whole app, moves the cache to another drive, and clears the cache for one project or for all of them. Clearing keeps files with edits that haven't reached the server. Until it ships, the limits above are fixed.

Work offline with a large project

Open the files and run the code you need while connected, so their content is in the disk cache. Datasets need the chunks your code will read; running the script once while connected brings them down. See Work offline and recover edits for what works during a disconnect.

On this page
  • Where project data lives
  • Large datasets load in pieces
  • How the disk cache cleans up
  • Change the cache size or location
  • Work offline with a large project