Desktop guide
Setup and troubleshooting
Start with a backed-up project. Review proposed operations before applying them, and check the result in UEFN. Undo availability depends on the operation; do not treat it as a project backup.
First connection
- Use the Windows download page. Check the displayed release details before running the installer. Do not bypass an unexpected signature or security warning.
- Open UEFN with the project you intend to edit, then open the desktop app beside it. Check the selected project and connection status before requesting changes.
- Start sign-in in the app. In the browser, sign in with Google and approve the desktop connection you just requested. Credentials expire after 30 days; reconnect when needed.
- For model requests, check Account for purchased allowance and Usage for gateway spend. A personal spending cap can be lower than the purchased allowance.
- Begin with a small supported change. Read the review and any irreversible-operation warning, apply only what you intend, and inspect compile or playtest evidence rather than assuming success.
Troubleshooting
Sign-in expired or never completed
Desktop approval links last 10 minutes. Open the link from the current sign-in attempt, check the browser account, and approve it. Start again if it expires. Do not share the approval URL or approve an attempt you did not start.
Too many requests (HTTP 429)
Wait at least one minute before trying again. Repeated sign-in attempts and rapid settings updates are throttled. Devices on the same network can share the caller limit; reopening many approval windows does not help.
Payment required (HTTP 402)
Sign-in does not grant model credits. Check Account for payment status and Usage for reported spend and the spending cap. The cap controls new request admission; in-flight requests and cost estimates can exceed it. Checkout returning to the site is not payment confirmation. Library-only sign-in does not grant model access.
Usage or settings unavailable (HTTP 503)
A gateway or server configuration problem can prevent usage reporting or provisioning. Retry later rather than buying more credits to fix a connection failure. If an approved sign-in expires, begin a new attempt. Unknown usage must not be treated as a zero balance.
Editor connection or operation blocked
Keep UEFN open with the intended project and check the app's connection and compatibility status. Support is operation- and build-specific: a readable project does not mean every mutation or playtest is supported. Review the app's blocked reason; do not bypass compatibility checks.
Lost device or sign-out could not confirm revocation
Open Usage on a device you trust and revoke each model and library credential associated with the lost installation. Model credentials also permit catalog reads. Revocation stops future authenticated use, not work already in progress. Website sign-out alone does not revoke desktop credentials.
Useful diagnostic details
Record the desktop version, UEFN build, the action attempted, the time and timezone, and the exact error or HTTP status. Redact project secrets, approval URLs, bearer tokens, payment details, and private source before sharing diagnostics.
A verified customer support contact and response-time commitment have not been published here. This page provides self-service guidance, not a staffed support promise. A request to delete an account or the private chat logs can be described here. That does not promise a staffed reply or a deletion deadline. The privacy policy and terms describe the website and the Windows app. They do not add a refund right or a response-time promise.