Exporting your data

Download table CSVs, app code and data, or user uploads. Check export limits before using them as backups.

To download a table, open Data, select the table and click Export. You get a CSV with up to 50,000 rows. Exports are free on every plan.

Export each table separately. For more than 50,000 rows, ask support about getting the remainder. The table export does not produce XLSX or JSON files; open the CSV in a spreadsheet app to convert it.

Download the app's code and data

Open Publish → Advanced Features → Export ZIP. The export runs in the background and emails you a download link valid for 24 hours.

The ZIP includes:

  • Currently saved app files, which may be newer than the published app.
  • App images and asset-library files; the README lists omissions.
  • Custom endpoint code in server/endpoints/ and scheduled tasks in server/scheduled/.
  • server/manifest.json with routes, sign-in settings, schedules and environment-variable names.
  • Database structure and data as SQL and JSON, up to 50,000 rows per table.

Environment-variable values, secrets and user uploads are excluded. GitHub export is rolling out separately and may not appear on your account.

Download user uploads

  1. Open Publish → Advanced Features → Download uploads.
  2. Wait for the email, then open its link while signed in to an account that can manage the app.
  3. Download within 24 hours of completion.

One download supports up to 1,000 files and 2 GB. Larger exports are refused. Each link click checks your permission; an unauthenticated script may reach sign-in instead of the ZIP.

The archive contains users' files. Do not share its download link or redirected storage address publicly.

Keep a useful backup

Wait for the builder to finish before exporting, then avoid further edits until the export completes. Read the README for missing assets and truncated tables, and download uploads separately.

The ZIP reads files and data while the job runs; it is not an atomic snapshot of the live app. Exporting does not publish or create a version. A code-version restore does not restore deleted records or uploads.

The built-in export controls are manual. There is no scheduled backup and no live sync to a spreadsheet.

Run an export elsewhere

An export contains your app's source and data. Moving it to another host also requires replacing or reconnecting platform services such as sign-in, storage, email, AI and payments.

Check the README and package.json for that app's dependencies. Copying server/ does not recreate the platform's endpoint wrappers or helpers, and there is no universal installation command.

See Importing data for bringing table data into an app.

Was this helpful?

Thanks for the signal — it helps us improve the docs.

More in Data and databases

Importing data into your app

Bring in data from a spreadsheet, CSV file, or another tool. Useful for migrating from existing systems.

Connecting Google Sheets and other spreadsheets

Overskill has no built-in spreadsheet sync. What actually works is a one-time CSV import, a CSV export, and integrations your app can call.

Storage and bandwidth

Every workspace includes 50GB of database storage and 100GB of file storage. Database storage past 50GB is billed at a small published rate; file storage past 100GB isn't charged today. Bandwidth is unlimited — no data-transfer or egress fees, ever.

Still need help?

If this didn't answer your question, our team is one click away.