File formats

Meridian document files

Each file is UTF-8 JSON. The current format version is 3. Meridian reads format version 2 and all later versions.

A part keeps its parameters, features, properties and simulation studies. Simulation results are not saved in the file.

The compatibility guarantee

A .mpart, .massy or .mdraw file that Meridian 2.0.41-alpha or a later release writes opens in each later release. You do not need to convert these files.

• A version 2 file opens directly, with no message.
• The file on the disk does not change until you save it. A save writes the current version.

Old version 1 files

Meridian 1.x wrote XML files (format version 1).

• Version 1 parts and assemblies are converted when you open them. The file on the disk does not change until you save. Meridian asks before it saves.
• Version 1 drawings (.mdraw), presentations (.mpres) and feature libraries (.mfeat) open read-only. Meridian shows their properties and a summary. It cannot save them.

To convert a file from the command line, use meridian convert. Refer to Command line.

Files from a newer version of Meridian

Meridian does not replace a file that a newer version wrote with a file that has less data.

If the file has only data that this version can read:

• The file opens. Meridian shows the banner "A newer version of Meridian wrote (file name). Some data can be missing. Update Meridian to edit this file."
• Save goes to Save As. Save the file with a new name, or update Meridian.

If the file has data that this version cannot read:

• The file does not open. Meridian shows "'(file name)' has format version N: a newer version of Meridian wrote it and it has data that this version cannot read. Update Meridian to open it."
• The file is not damaged. Update Meridian to open it.

Components that do not load

If a component file of an assembly is missing, damaged, or from a newer version, the assembly still opens. The component stays in the assembly with its path, position and state. When you save the assembly, Meridian keeps the component.

Meridian shows a warning banner with one line for each component that did not load. The tooltip of the component in the model browser gives the cause.

Exchange formats

These formats are for exchange with other programs. The compatibility guarantee does not apply to them.

An imported STL or OBJ mesh can be a reference body or a solid body. A STEP file with a product structure can become an assembly.

Simulation result files

You can export study results as CSV, or as VTK for ParaView. You can save a study report as HTML or Markdown. Refer to Structural simulation.