Retool Storage is now available to self-hosted organizations as a file management interface for an S3 or Google Cloud Storage bucket. Because you control your own file storage bucket on self-hosted deployments, there are no data limits or overages for Retool Storage on self-hosted deployments.

Retool Storage for self-hosted deployments is available in the current Edge release and in the next Stable release.

You can now set private or public access for files uploaded to Retool Storage. Each file in your Retool organization has a public URL that you can enable by making the file public.

Files uploaded to Retool Storage are private by default, and you can switch between private or public access at any time. When uploading files with a Retool Storage resource query, you can enable Make file public on upload to automatically make them public.

Retool Storage is a hosted blob store that allows you to upload and interact with your files without needing to configure an object store (e.g., S3, Azure File Storage). There is a 5 GB storage limit per organization, with a 250 MB limit on file size. Your browser may have settings that restrict this limit further.

Working with files has previously been a challenge for users as it required storing base64 strings or using third-party data stores. Retool Storage is a built-in solution that requires no configuration.

There are two ways to interact with Retool Storage:

• The Retool Storage section in the Resources tab for your organization.
• The Retool Storage resource, available in both apps and workflows.

You can programmatically upload, read, and download from Retool Storage.