Common problems

When something fails, identify the category, apply the shortest reliable fix, and confirm the app is healthy before you continue designing.

App does not startlink

Browser compatibility, missing cross-origin isolation, or WebAssembly memory limits can block the first load. Refresh once. Use a current Chrome or Edge build. Try a smaller font if memory is tight. SharedArrayBuffer is required.

Disk folder is not accessiblelink

Permissions expire, get revoked, or fail after a browser session change. In Files → Disk, click Re-enable access, select the same folder, and allow read/write. Details are in Local disk access.

Script or filter failslink

Usually a syntax error, an unexpected property, or calling Glyph() / Layer() outside outline editing. Shrink the test, read the first line of the error, and try the same call in Konsole. Filters must not edit the font.

AI assistant is unavailablelink

You may be signed out, missing the Advanced plan or trial, or out of usage. Confirm login, check subscription in account management, and read any usage warning. See Subscription and usage.

Cloud font is read-only or will not synclink

Viewers, revoked invites, this browser being unable to store unsent edits, the server still catching up, and a required update all leave a cloud font read-only. Check the title-bar connection reason. Sign in again if the session expired. Update the editor if it asks for a reload. Pending edits live in this browser until they sync; another device will not have them. See Cloud fonts.