Design load failure when opening legacy Canva designs in current editor

Direct answer

Canva does not publish a compatibility matrix or numeric editor version thresholds that cause the Design Loader to reject legacy designs. The likely explanation is that the loader reads an internal metadata field—commonly formatVersion—and compares it against a supported range defined in the editor's configuration. Designs with a formatVersion below the current minimum are rejected with a generic load-failure message, while designs newer than the maximum supported version wait for an editor update. Because Canva ships continuously and does not document these values, no fixed threshold is reliable across releases.

Confirmed facts vs. likely mechanism

Confirmed: The load failure is generic and does not include a version-specific message. The behavior can change with each deployment, so a design that fails today may load after a future editor update without any change to the file.

Likely (not officially documented): The rejection is driven by a formatVersion range check. The supported range is updated with each major editor release: the maximum is usually the current design format, and the minimum is the oldest format the editor was built to import. Out-of-range values abort loading.

Steps to detect incompatibility before load

1. Export the legacy design as a JSON file.
2. Parse the formatVersion field from the exported metadata.
3. Obtain the current editor's supported range—minSupportedVersion and maxSupportedVersion—from a public compatibility endpoint or a configuration file bundled with the editor. This is an inferred source and may change without notice.
4. Compare the design's formatVersion against that range.
5. If the value is below the minimum, invoke Canva's conversion API to transform the design into the current format, then reload. If it is above the maximum, wait for an editor update.

Important caveats

• Relying on inferred metadata names such as formatVersion is risky; Canva may rename or restructure internal fields.
• The conversion path may not preserve every design feature, so fidelity loss is possible even after a successful conversion.
• Because the exact thresholds shift with each release, any pre-load check must be performed against the editor's configuration at the time of load.

Missing diagnostic detail

One missing diagnostic detail would change this recommendation: does the design's JSON export actually expose a formatVersion field? If it does, the comparison workflow above is viable. If it does not, programmatic pre-load detection is not possible with the current information, and the safer path is to attempt conversion or open the design in a controlled session to observe the failure.