Exports preserve your data structure and content but exclude certain elements like row comments and revision history.
Download table data in CSV, Excel, JSON, or XML format for backups, external analysis, or sharing. Export entire tables or specific views with all visible data and configurations.
Exporting creates downloadable copies of your table data in formats compatible with spreadsheet applications, databases, and analysis tools. You can export entire tables with all data or specific views that contain only filtered and sorted subsets. Exports capture the current state of your data, making them perfect for backups, reporting, or transferring information.

Included in exports: All field values in visible rows, field names as column headers, row order based on current sorting, and data formatted according to field types (dates, numbers, text, etc.).
Excluded from exports: Row comments and mentions don’t export since they’re metadata about rows rather than row data. Row revision history and audit logs also stay in Baserow. Collaborator information and user assignments are excluded, though the data in collaborator fields exports as names or emails.
Filter behavior: View exports respect active filters in your current view. If you’ve filtered to show only rows where Status equals “Active,” your export contains only those active rows. This is powerful for creating targeted reports, but it can accidentally exclude data if you forget about active filters. Remove all filters before exporting if you need complete table data.
Each format serves different purposes and works best with specific tools or workflows.
Exporting the full table captures all data regardless of current filters or views, giving you a complete backup or dataset.
⋮ icon next to the table name in your sidebarThe export includes every row and field in the table with current values as of the export moment.
Exporting views captures only the data visible in that view, including applied filters, sorts, and field visibility settings. This is perfect for creating targeted reports or sharing specific subsets of data.
Learn more about views: Export views
Regular backups: Export entire tables as CSV or Excel monthly or weekly, depending on data change frequency. Store exports in cloud storage or backup systems for disaster recovery. Consider automating exports through the API for critical tables.
Sharing with external stakeholders: Create filtered views showing only relevant data, then export those views to share specific information without exposing your entire database. Use Excel format for polished presentations or CSV for simple data sharing.
Data analysis in other tools: Export to CSV for universal compatibility with analysis software, BI tools, or statistical packages. Remove filters to ensure you’re analyzing complete datasets rather than subsets.
Migration or archiving: Use JSON format for complete data structure preservation when moving data between systems or creating archives. JSON maintains data types more reliably than CSV for later re-import.
Periodic reporting: Set up views with specific filters and sorts that generate your standard reports, then export those views on a schedule (weekly sales reports, monthly inventories, etc.). The same view exported at different times creates consistent report formats with updated data.
Link to table fields export as references showing linked record IDs or primary field values. The actual data from linked tables doesn’t export automatically. If you need complete information from multiple linked tables, export each table separately and use IDs to match records in your analysis tool.
No, Baserow exports one table at a time. To export multiple tables, repeat the export process for each one. For complete database backups including multiple tables, consider using the database or workspace export feature, which bundles all tables together.
Formula fields export their calculated values, not the formulas themselves. If a formula calculates “15” based on other fields, the export contains “15” as static data. The export doesn’t preserve the formula logic or update automatically if the source data changes.
Export size depends on your data volume and format. CSV files are the most compact, while Excel and XML are larger. Very large tables (tens of thousands of rows) may take several minutes to export and result in large files. Consider filtering exports or splitting large tables if the file size becomes problematic.
Manual exports work well for occasional needs, but frequent exports benefit from automation. Use the Baserow API to programmatically trigger exports on schedules. This is particularly useful for daily or weekly backups, regular reporting, or integration with external backup systems.
Work with exported data:
Related table operations:
Alternative approaches:
Still need help? If you’re looking for something else, please feel free to make recommendations or ask us questions—we’re ready to assist you.