Summary

Starting from xTool Studio v1.7, newly saved projects will use a new file format: .xs.

Older .xcs files can still be opened and edited in version 1.7 and later. However, .xs files can only be opened in v1.7 or newer.

If compatibility with older versions is required, you can still export projects as .xcs files, although some new content or effects may not be fully preserved.

What Is the New Project File Format?

Beginning with xTool Studio v1.7, newly created projects will use the new .xs project file format by default.

This upgrade is not just a change of file extension — it is designed to make project saving, synchronization, cloud recovery, and large project handling more stable and efficient.

Why Upgrade the Project File Format?

As projects become increasingly complex, the old file model has gradually exposed several issues, such as:

• Inconsistent rules between local saving, cloud saving, and file exporting
• Higher costs for saving, uploading, and opening large projects
• Long-term compatibility requirements making the internal model increasingly difficult to maintain
• Difficulty determining whether issues originate from editing, local files, exported files, or cloud versions

The new project file format is intended to clarify these boundaries and establish cleaner rules for editing, saving, syncing, and recovery.

What Changes After the Upgrade?

Starting from v1.7:

• New projects are saved as .xs by default
• Older .xcs files can still be opened and edited in v1.7 and later
• Older Studio versions cannot open .xs files
• Projects can still be exported as .xcs for compatibility with older versions

Can Old Projects Still Be Used?

Yes.

Existing .xcs files can still be opened and edited in v1.7 and later.
However, in the current version, legacy .xcs projects can no longer be saved directly in that format. To preserve all content, please save the project as .xs instead.

Can Older Versions Open .xs Files?

No.

.xs files are only supported in Studio v1.7 and later. Older clients cannot recognize or open .xs files.

For older software versions:

• v1.6 will prompt users to upgrade
• v1.5 and earlier versions will display an error directly

Can Projects Still Be Saved or Exported as .xcs?

Yes, but this is mainly intended for backward compatibility.

When saving, using “Save As,” or exporting locally, the default format option is .xs, but you can manually switch to .xcs.

However, please note:

Some data or effects supported only in newer versions may not be fully preserved when saving in the old format. Certain content may change or be lost.

The documentation also lists some content that cannot be saved in the v1 format, such as:

• Certain new object types introduced in v1.7+
• Some processing parameters and device data

How Will Cloud Files Be Affected?

Starting from v1.7, all cloud files will be saved in the new format.

Older software versions can still see these cloud files in the file list, but they cannot open cloud files saved by newer versions.

When opening an old-format cloud file in v1.7 or later, the system will first prompt you to upgrade it. By default, the system recommends keeping the original backup.

If this option is selected:

• A copy of the original cloud file will be preserved
• The original file remains unchanged
• Users can still access the old version later if rollback is needed

How Does This Upgrade Relate to Version History?

To reduce the risk of cloud file data loss caused by abnormal saves, v1.7 also introduces Version History.

In Version History, you can:

• View previous versions
• Restore to a specific version
• Create a copy based on a historical version

Rules for generating version history include:

• A history record is created the first time a cloud file is opened in v1.7
• Each manual save creates a new version record
• Auto-save does not frequently create versions, but accumulated saves will eventually generate a new record
• Saving triggered when closing a project or exiting the software will also generate a history record