While looking into ways to export or copy Retool release history, I ended up implementing a small pattern that worked well for us and documented it here:
A Structured GitHub Archive Pattern for Retool Releases
In short, the approach is:
- Export the app JSON for each release
- Store those exports in a Git repository (we used GitHub)
- Organize them chronologically and optionally by module
- Use Git for searchable diffs, history exports, and long-term archival
If you plan ahead, exporting the JSON after each published release makes this straightforward. In our case we reconstructed history retroactively by reverting to older releases, exporting them, and then restoring the latest version.
This ended up giving us a structured, searchable release archive outside the Retool UI.
Hope that helps anyone else looking for a similar approach.