Multipage apps are now generally available. Any new Retool apps that you create will support multiple pages by default. The creation of single-page apps is still supported but they are now considered legacy. Multipage for mobile apps remains in beta.

Building apps with multiple pages enables you to combine functionality and use cases. Retool only evaluates the code and components of the page currently in view, providing the following benefits:

• Greater performance of large and complex apps. Since Retool only evaluates code and components for the current page, apps can perform 30-40% faster.
• Seamless navigation between pages. Navigation between pages is seamless and more responsive than before as Retool only evaluates the current page, not the entire app.
• Improved app management. Multiple pages can replace multiple apps in your organization, such as a team's frequently used apps. This reduces the number of apps to maintain and allows for easier permission management.
• Reduced module dependency. Modules are commonly used to create shared navigation menus across multiple apps. With multiple pages, you can eliminate the need for additional modules and the complexities with maintaining them.

Each app uses global and page scopes to separate pages. Globally scoped code, and Header and Sidebar frames, are available for use across every page, while each page has its own page-scoped code and components.

Improvements to the Navigation component are now available. When you add a Navigation component to an app with multiple pages, Retool automatically configures the menu items to map to the pages of your app. Event handlers are also preconfigured, and clicking a menu item takes you to the corresponding page.

You can still customize the Navigation component to have different behavior, if desired. Refer to the Navigation guide for more information.

This change also made retoolContext.pages and retoolContext.currentPage available. Refer to the Retool Context reference for more information.

Due to potential security concerns, Retool is removing certain functionality that enables external app users to download images. No security breach or active vulnerability has occurred, and you do not need to take any security-specific actions.

External and embedded, publicly available apps will no longer support:

• Download Image columns in the Legacy Table component. Use an alternative method, such as a Link or Button column type, for image URL links. Retool strongly recommends you migrate to the current Table component instead.
• Export PDFs with images hosted on separate domains. All other components will be included in the PDF export. Retool recommends moving your publicly-hosted images to be hosted on the same domain as your Retool instance. For example, you could use images that are natively uploaded to the Image component, stored in Retool Storage, stored in Retool Database, Base64-encoded, or stored in an Amazon S3 bucket.

A new and improved version of the Checkbox Tree component is now available on Retool Cloud and for self-hosted organizations.

The new Checkbox Tree features:

• The ability to use manual or mapped option lists.
• Validation rules.
• Captions, tooltips, and other customization options.
• Support for infinite nesting.

Apps that contain modules are now much more performant and can load up to 1.5–2x faster than before. For self-hosted organizations, these improvements also reduce the resources needed by apps and modules, such as CPU load.

You can now copy a query from one multipage app and paste it into another. Right-click on a query and select Copy then navigate or switch to a tab with another multipage app. You can paste the copied query as either a globally scoped or page-scoped query by right-clicking in the Code panel.

You can set up integrations with Datadog and Sentry. With these integrations, app errors are reported with a callstack and descriptive tags when you view and interact with an app in preview or public (end-user) mode.

To connect third-party observability providers, you can report app errors using Retool Events and build a workflow that triggers whenever an app error occurs and automatically notifies your observability provider.

Retool now supports 15 preset chart components, eliminating the need to manually write Plotly JSON for basic chart types. This change enables users to more easily create and customize chart and graphs in their apps.

Features of the new chart components include:

• Support for multiple data sources in series-based charts.
• Data grouping and aggregation.
• Customizeable titles, legends, labels, and toolbars.
• Configurable user interactivity.
• Advanced use cases using the Plotly JSON Chart.

An updated Theming experience is now available. Users on the Business and Enterprise plans can now see a revamped organization-level theme editing experience with expanded functionality, including:

• The ability to create custom color, typography, and metric tokens for use in the theme editor and app component styles.
• The ability to create multiple modes within a theme and switch between modes in an app using theme.setMode().
• The ability to configure default styles for individual components, as well as bulk edit shared styles for multiple components at once.
• Expanded typography controls—including the ability to configure multiple fonts in a theme using a CSS import or Google Fonts, set a default font family, and control font family and font weight for headings.

For users on all plans:

• Component-level font weight and font family style controls.
• A refreshed app-level theme experience with expanded typography controls.
• An updated component style editing experience.

Retool will deprecate the use of YAML for protected apps, queries, and resources in Source Control. Support will be removed in the Q2 2025 stable release of Self-hosted Retool.

Self-hosted organizations still using YAML serialization of these elements in Source Control must migrate to Toolscript prior to upgrading.