Saving and opening projects#

Use a GraphX project when you want to continue editing a graph later, transfer the complete working state to another browser, or keep the calibration and point placements alongside the source image. For the distinction between a project and an export, see Projects overview.

Save a project#

With an image open, select Save project in the application header. GraphX prepares a self-contained .graphx file containing the original source image and the persistent project data. A successful save clears the unsaved-change indicator; it does not close the workspace or change the project name.

Project download names use the project name and the local browser save time, for example:

Solubility study - 2026-09-19 203152.graphx

The timestamp is created when you save, so repeated saves naturally create separately named downloads. The project name stored inside the file remains the authoritative project name; the timestamp in a download filename is not added to the name when you open it again.

On desktop browsers, the file is normally delivered through the browser's usual download mechanism. On iPhone and iPad, GraphX prepares the file for the native share/save sheet; after preparation, choose Save to Files and select a destination. Cancelling that sheet leaves the project open and does not mark it as saved.

Open a project#

Select Open project, choose a .graphx file, and let GraphX validate it before replacing the workspace. A successful open restores its embedded source image, calibration, axis details, datasets, points, project notes, and trendlines. GraphX then fits the restored image into the workspace.

The .graphx extension is specific to GraphX. Your operating system may show it as an unknown file type or may not associate it with an application; open it from GraphX rather than relying on a double-click association.

GraphX also provides Load sample project from the welcome workspace. The bundled sample uses the same validation and restore path as an opened project.

Validation and compatibility#

GraphX validates both the project structure and its embedded image. Renaming an arbitrary JSON file to .graphx does not make it a valid project. Damaged files, unsupported newer project formats, invalid embedded images, and oversized projects are rejected without partially replacing the current workspace.

Current GraphX project files use a versioned format. Earlier files from before project names, notes, dataset precision, explicit Export settings, or first-class trendlines are normalised where the current format has a safe default: for example, a missing name is derived from the image name, notes start empty, datasets default to Export enabled, and legacy per-dataset trendlines are restored as current trendlines. GraphX does not promise that every future version can open every historical file indefinitely.

On iPhone and iPad, the project picker may show more than just .graphx files. This helps the Files picker remain usable with a custom extension; GraphX checks the selected file after you choose it.

Unsaved changes#

GraphX shows an unsaved-change indicator when the persistent project state differs from the last successful save or load. Typical causes include changing the project name or notes, calibration or axis details, datasets, point data, precision, Axis lock settings, trendlines, or relevant saved display settings. Purely temporary actions such as pan and zoom do not make a project dirty.

If you try to open another project or load the sample while the current project has unsaved changes, GraphX asks before discarding that work. Cancelling keeps the current project unchanged. The same protection is used when a destructive replacement would discard modified work. Saving successfully establishes a new clean baseline.

Project notes explains the notes that travel with a project and Export overview explains how outputs are produced without replacing it.