Troubleshooting and recovery

After a crash or interrupted session

At the next launch, select the recovery documents you want and choose Recover. Unselected documents are kept for a later launch; discarded recovery data is not a backup.

Recovered documents open unsaved. Use Save As to choose a destination and check the content before replacing an existing project. Regular project copies remain useful alongside automatic snapshots.

A tool does not change the image

• Check the active document and selected layer.
• Select the pixel thumbnail or the intended mask thumbnail.
• Check visibility, locking, opacity and the active selection.
• Some tools require a raster layer, a source sample or an applicable text/path context. Use command search or the menu’s availability state to identify the required context.

A file fails to open or save

For a newer .focale format, use an application version that understands it. For damaged data, preserve the original and investigate a copy. A ZIP that contains manifest.json is not automatically a valid project.

For saving, verify the destination is writable and has enough free space. Large dimensions, deep samples and many layers can exceed the configured payload or format bounds. A browser’s storage quota is separate from free disk space.

Fonts or colours look different

Install the font families used by the document and review profile assignment, conversion and proofing options. Unsupported PSD/PSB features may be shown as stored pixel previews.

A linked smart object needs its source file. Relink or embed it when moving work between machines. Compare exports in an application that honours their colour profile.

Error reporting and local work

Editing and document processing are local. Builds configured for error reporting can send technical error events when Preferences → Diagnostics → Send error reports automatically is enabled.

Screenshots and document content are not deliberately attached, but native crash dumps can contain fragments of process memory. Disable automatic reporting in Diagnostics if you do not want new reports sent. On Linux and Windows, restart after re-enabling to restore native crash capture.

Prepare a reproducible report

Record the application version and build, operating system and processor, exact steps, format and approximate document dimensions, the error text and whether the problem affects a small new document.

Use a minimal non-sensitive example or a screen capture you have checked. Avoid sending private projects or recovery folders by default. Note any third-party fonts, linked resources or imported preset libraries involved.