Publish an app

Publish and share an app with your organization.

By default, all apps are created in your Drafts folder in an unpublished state. In order for other users to see and use your app, you must publish it.

You must be a builder to publish an app. Internal users can create apps, but they cannot publish them.

If you prefer to use Source Control to manage changes to your apps, refer to the Source Control guide.

Publish your app

To publish your app, click Publish in the top right corner of the app builder. Complete the following steps in the modal that appears:

1. Review the Publish checklist. Retool performs several checks to ensure that your app is ready to publish:
   • All function runs are approved. If there are unapproved functions, click Review functions to view the functions that still need approval.
   • Your changes do not conflict with the published version changes from other users. If there is a new published version of your app, click Integrate changes to ask the agent to resolve the conflict.
2. Define a descriptive name for the App URL.
   • For cloud instances without custom domains, URLs are constructed in the following format: <orgSubdomain>--<appName>.retool.app.
   • For self-hosted instances or cloud instances with custom domains, URLs are constructed in the following format: https://example.retool.com/rr/app/<appName>.
3. Choose the folder in which you want your published app to be available, and confirm your selection. All users with use access to the folder you select will be able to use your app.
4. Optionally, expand Releases and choose whether you want to tag this release with a new semantic version. By default, the new release is not tagged. Learn more about release tagging.
5. Click Publish.
6. Click Copy link to copy the link to your published app.
7. Once you publish your app, your thread is considered closed, and further prompting is disabled. Click Start new changes to continue iterating on your app.

Tag a release

By default, when you create a new version of your published app with no tag, end users are automatically shown the most recent published version of your app. To show app users a particular published version of your app, tag a new release.

You can tag a new release during the publishing process, or tag a previously published version using the following steps:

1. In the navbar, click to open the Version History pane. Switch to the Publish history tab, which shows all published versions.
2. Find your desired published version, and click the icon.
3. In the Publish release modal that opens, choose whether you want to tag your release as a Major, Minor, or Patch version.
4. In response to Which version should be published?, choose one of several options:

• Latest commit: The latest published version will be tagged as the new release, and all future published versions will be automatically released to users.
• This tagged release: This published version will be tagged as the new release, and all end users of your app will see this version.

5. Click Tag release.

Restore a previous version

You can restore a previous version of your app to your current thread. Restoring enables you to continue making changes from that version. You can restore a published app version, or you can revert to a certain point in an existing thread.

Restore published version

To restore a published version to your thread, use the following steps:

1. Ensure that there's an open thread in the Chat tab.
2. In the navbar, click to open the Version History pane. Switch to the Publish history tab, which shows all published versions.
3. Find your desired published version, and click Restore. After a few moments, the preview canvas updates to show that version of the app. The older version is restored to your thread only—the published version remains the same.
4. You can then make any further changes to your app, and publish when you're ready.

Restore from Chat tab

While prompting from the Chat tab, you can restore the app to a previous state in your current thread. Each time the agent finishes making changes, it presents a summary of the changes and a Restore button. Click this button to return your app to the state it was in when the agent finished those changes.

You can then make any further changes to your app, and publish when you're ready.

Capabilities and limitations

The following tabs show a summary of the current capabilities of the app builder. Limitations describe functionality that isn't yet supported in apps but may exist in classic apps.

Capabilities

• Publish an app to a specific folder in the organization.
• Define a custom App URL for each published app.
• Use the Publish checklist to confirm there are no conflicts and that all functions are approved.
• Restore a previous version of an app from the Publish history.
• External users (who have email domains from outside your organization) can view published apps.
• Publish an app on a custom domain. Refer to Publishing on custom domains for more information and limitations.

Limitations

Some functionality is not currently supported:

• Embedded apps in external websites or applications.
• Public links to apps.
• Exported apps for use outside of Retool.
• Shared draft apps before publishing.

Publishing on custom domains

If you self-host Retool (which uses domains you define) or use a custom domain on a cloud instance, your apps are published to the domain you define in the following format: https://example.retool.com/rr/app/<appName>.

In these scenarios, Retool runs your app inside a sandboxed iframe with allow-same-origin disabled. This provides additional security to isolate published apps from your Retool instance. However, because of this security mechanism, there are certain limitations that apply to published apps on custom domains.

Browser feature limitations

The sandbox has no persistent origin, so features that depend on storage, cookies, service workers, or device access are unavailable:

Category	Unavailable
Storage & cookies	localStorage, sessionStorage, IndexedDB, Cache API, persistent/Storage Access APIs. Cookie reads return empty and writes are ignored. Cookies aren't attached to the app's requests.
Background & coordination	Service Workers (and everything built on them, such as Push, Background Sync/Fetch, PWA install), BroadcastChannel, SharedWorker, Web Locks, Notifications.
Identity	WebAuthn/passkeys, Credential Management, FedCM, Web OTP, Cookie Store.
Media & clipboard	Camera, microphone, screen capture (getUserMedia, getDisplayMedia), DRM playback (EME), clipboard reads.
Files & windows	File System Access dialogs, top-level navigation (top.location), parent/top window access.
Hardware	WebUSB, Web Serial, WebHID, Web Bluetooth, Web MIDI, motion/environment sensors, Gamepad, WebXR.
Other	Payment Request/Handler, Web Share, Contact Picker, Idle Detection, Window Management, Local Font Access.

Widgets that rely on their own cookies, storage, or login session (such as Stripe Checkout, Calendly, embedded OAuth/SSO dialogs, and reCAPTCHA) may render, then fail when their storage is unavailable. This applies to any nested frame, regardless of origin. To present this content, builders should instead create resources, which are supported and leverage Retool's native authentication mechanics.