Settings tab

Experience level

This core reference entry is suited for beginner to intermediate-level builders.

In-depth articles (3)

To learn about this topic more in-depth, we recommend reading the suggested articles below:

The settings tab

This article covers the interface of the Settings tab in the Bubble editor.

Article: The settings tab

Setting up a custom domain

This article covers how you register and manage a for your app.

Article: Setting up a custom domain

Controlled updates (Enterprise plan)

This article series covers how you can gain a greater control over updates applied to the Bubble codebase. This subject is applicable to users on the Enterprise plan only.

Article series: Controlled updates on the Bubble enterprise plan

Overview

My plan

This is where you see which Bubble app plan your current app is on. Remember that Bubble plans generally apply at the app, not the account, level. In this sub-tab, you can see some of the capabilities of your current plan and change your plan as desired.

• Plan

• Workload

• Storage

• Plugins

General

This sub-tab contains a mix of different settings—some design-oriented, some privacy-oriented, some app-level management oriented.

• Privacy and security

• General appearance

• • Google Geocode API key

  • Google Maps API key

  • Google Maps key for iOS

  • Google Maps key for Android

  • application ID

  • Algolia Search API key

  • Algolia admin API key

• iOS appearance

• Custom fonts

  • Lets you upload to use in your app.

• Design import from Figma

  • Lets you

• App file management

• Advanced options

  • Time zone controls

  • Exposing HTML element IDs

Other settings.

Don't allow file uploads to the file upload API endpoint

This setting disables the fileupload API endpoint, which can improve security by preventing direct access to that upload route. However, it does not disable all file uploads—it only blocks access via the fileupload endpoint, which certain plugins and workflows rely on.

How this affects file uploads:

• If the checkbox is checked (i.e., the fileupload endpoint is disabled) file and image uploads will work as usual:

  • File and image uploads through the Bubble editor still work—this includes actions like setting images in the property editor or uploading directly to the File manager (if the collaborator has permission to edit the app's data)

  • File and image uploads in runmode using Bubble elements like the File uploader and Picture uploader also continue to work (unless they are prohibited by conditions or privacy rules), with the following exceptions:

    • Picture uploader: if limit image size before upload is enabled, it will not work.

      • Non-standard upload location: if you are using a non-s3 storage (e.g. Box), it will not work.

  • The fileupload endpoint remains disabled for all other access, including for plugins or custom calls—this may cause certain Bubble-built or third-party plugins to stop functioning if they depend on it.

• If the checkbox is unchecked (i.e., the fileupload endpoint is enabled):

  • There are no restrictions on file uploads—any part of the app or plugin can use the endpoint as usual.

  • Be sure to test any functionality that depends on file uploads—particularly plugins or custom workflows—before enabling or disabling this setting.

Do not send an email when the application is being rate-limited for map loads

If you have your Google keys set up, your app will use those keys when making requests from Google Maps and Geocode. Google rate-limits these requests, and by default, you (the app creator) will receive an email from us when the application is being rate-limited. Checking this box will disable that email.

Algolia

See this article on how to set up the integration between your app and Algolia.

Prevent clipping fields on rows too large to fit in Algolia (advanced)

Algolia has a default size limit for data fields that are sent to it. Bubble implements clipping correspondingly to help Bubble apps stay under that default size limit. However, advanced users may not want Bubble to do this for various reasons, and can use this setting to control that.

Optimize application

Over time, as many changes are made to your Bubble app, the application will remember information about parts of it that may no longer be relevant (e.g. a style that used to exist but no longer, or a data type that used to exist but has since been deleted).

This tool in the General tab will help you clean some of that unused content out, which could improve performance of your app overall. Note that doing so will prevent you from certain actions, such as restoring a deleted data type, if you've cleared out the history of that deleted data type.

Clean app changes history

Clearing your app history removes all saved history and cannot be undone. See the table below for details on which data is affected.

This feature removes the saved history of changes to your app. If you no longer need this history—which allows you to revert your app to a previous state—you can clear it to improve editor performance.

Feature	Affected by clearing app changes history
Undo history	❌
Revert app to custom date/time	✅
Revert app to custom save point	✅
Version Control changelog	✅

Export application

Bubble apps can be exported as a JSON file - please see this article.

Import application

If you have the JSON of a Bubble app (e.g. from exporting a Bubble app, see above), you can import it into the current app with this feature.

API

APIs is a broad subject, and for new users it can be one of the more complex areas of Bubble to learn. Still, it's also one of Bubble's most powerful and exciting features that open up your app to work together with other systems all over the web.

The article series below takes you through what APIs are, the different types of APIs and how to set it all up in Bubble.

Article series: APIs

Bubble apps come with APIs, which allow your app to connect with other web services. This sub-tab is where you turn the app's APIs on or off, as well as control what's available through the APIs.

• Enable and backend workflows

• Enable

• Use field display instead of ID for key names

• Hide API documentation access

Generate a new API token

Once you've turned on at least one of your app's APIs, you have the option to generate a new API token. This is one of the ways a call to the API can be authenticated. See the API reference. Live).

Tip: You have access to this option when you are an admin of the app's current version (e.g. Development or

Caution: Using the API token feature allows for a lot of flexibility with inbound API connections, but it also opens up for potential security vulnerabilities as it gives the broadest possible access to your app's API.

If you are not entirely sure of the implications of this, we recommend reading the guide below to learn more about how the different authentication methods affect your app's security.

Article series: API authentication

API token label and private key

For each API token you choose to create, you are able to supply a custom label for it, which makes it easier for you to remember where each token is used, for example. Regardless, you will also see the private key itself.

Collaboration

On certain higher app plans, you can invite other Bubble users to collaborate with you on your app. This is where you can control who your collaborators are and what privileges they have on the app.

User manual article: Collaboration in Bubble Core reference: List of collaboration settings

Languages

This sub-tab contains Bubble's feature to help you localize your app to different languages. Here, you see different "app texts"—snippets of text that appear throughout your app, some of which are built-in, others from plugins, and still others that you define. For any of these snippets, you have the opportunity to provide the translation of that snippet into any other language that Bubble supports out of our catalog of several dozen.

User manual article: Translating your app

Import and export

To facilitate changing many App Texts at once, you can import and export all the App Texts from one or more languages as a CSV. If you are planning to import, we recommend you first do an export to get the expected structure of the CSV file for the import

User manual article: Translating your app

Sub apps

is an advanced feature that lets you connect one app with another in a parent-child relationship, and changes to the parent can be 'pushed' to the child.

Copy DB for creation

When you first create a sub app, you have the option of copying the parent app's database to the sub app with this checkbox.

Push to sub applications

This section lets you push changes from a parent app to its sub apps. Please refer to this article to understand what does vs does not get pushed.

Versions

Bubble generally rolls out updates to the platform many times a day and there is no need for you to do anything in order to receive those updates. However, on rare occasions, an update might introduce a "breaking change" that could alter your app's current functionality.

For these specific changes, you'll need to actively upgrade your Bubble version, which can be done within this section.

Applications on the Enterprise plan have a greater degree of control over when updates are applied to their app. You can read more about it in our articles series about Bubble for Enterprise.

Article series: Bubble for Enterprise

Notifications

You can set up custom notifications for unit consumption. This lets you stay on top of your spending.

Web app

SEO and metatags

• Social media/OpenGraph settings

SEO settings

Advanced settings

301 redirections

Set up permanent redirects from one URL to another. Helps preserve SEO value and ensures users land on the correct page when URLs change. This is also useful when you are migrating from another platform.

Hosting files in the root directory

Upload static files to be served from the root of your domain (e.g. yourapp.com/filename). Useful for domain verification or third-party service integration.

Domain and email

Settings for connecting your app to a custom domain. See the article below for an in-depth guide:

Article: Custom domain and DNS

Native mobile

This is the short-form core reference explanation of each setting in the native mobile settings category. For an in-depth look at how to publish your native mobile app in the app stores, see the article series below:

Article series: Publishing your native mobile app

Basic details

Apple App Store settings

• App Store Connect API

• Apple push notification service

Android Play Store settings

• Firebase cloud messaging

Builds and live versions

This section lets you manage how your mobile app is deployed. You can submit new builds to the app stores, track and manage live versions, and send OTA (over-the-air) updates.. Use it to control what your users see, roll out updates, and handle version support across different devices.

Device permissions

Control which device features your app requests to ensure transparency for users and meet app store requirements.

Supported languages

Select the languages your app supports to provide clear localization for users and meet app store listing requirements.

• Add new language