Export views from Baserow

View exports let you share exactly what you see, filtered, sorted, and formatted, without exposing entire tables.

This guide covers how to export filtered, sorted, or customized Grid views to CSV, Excel, JSON, or XML for sharing specific data subsets.

View export is currently available only for Grid views. To export from other view types, switch to Grid view first or use table export.

Selecting a view to export

What are view exports?

View exports capture exactly what you see in a specific view, including filters, sorts, hidden fields, and row selections. This makes view exports ideal for creating targeted reports, sharing relevant data with stakeholders who don’t need full table access, or generating recurring reports with consistent formatting.

Unlike table exports that contain all data, view exports give you precise control over what information leaves Baserow.

View exports vs table exports

Choose the right export method based on what you need to share:

Aspect View exports Table exports
Data included Only visible, filtered rows All rows regardless of filters
Fields included Only visible columns All fields including hidden ones
Row order Matches view sort Default table order
Available from Grid views only Any view type
Best for Targeted reports, specific datasets Backups, complete data transfers
Updates with filters Yes, respects current filters No, always exports everything

When to use view exports:

  • Monthly reports with consistent filtering
  • Sharing data with external stakeholders
  • Department-specific datasets from master tables
  • Recurring exports with stable formatting

When to use table exports:

  • Complete data backups
  • Migrating entire datasets to other systems
  • Archiving comprehensive historical data
  • When you need everything without filtering

Learn more: Export entire tables

How to export a view

View exports work through the view settings menu, giving you format and configuration options before downloading.

Step-by-step process

  1. Open the view you want to export
  2. Click the ellipsis ••• beside the view name to open view settings
  3. Select “Export view” from the menu
  4. Confirm the view selection in the dropdown (it should show your current view)
  5. Choose your export format (CSV, Excel, JSON, or XML)
  6. Configure format-specific options if applicable (CSV delimiters, encoding)
  7. Click “Export” to download the file to your device

The exported file respects all view configurations active when you initiate the export. Filters, sorts, hidden fields, and row groupings all influence the final export content.

Export formats and options

Each format serves different purposes and offers specific configuration options.

CSV (Comma-Separated Values)

CSV is the most configurable format with options for delimiters and encoding. When exporting to CSV, you can customize how data is structured.

Column separator options: The default comma (,) works for most uses, but you can choose alternatives. Use semicolon (;) for European systems where commas indicate decimals, pipe (|) when data contains many commas naturally, tab (<tab>) for tab-delimited files preferred by some database systems, or record separator (30) and unit separator (31) for specialized technical requirements.

Encoding options: UTF-8 (default) handles all international characters and emojis correctly, making it the best choice for most scenarios. Latin-1 may be needed for legacy systems that don’t support UTF-8, while other encodings exist for specific regional or technical requirements.

Header row: Baserow includes field names as the first row by default, which helps when importing into other systems. Most applications expect headers, but you can disable this option if you need pure data without column labels.

Excel (.XLSX)

Excel format preserves formatting better than CSV and opens natively in Microsoft Office. It supports multiple sheets, though Baserow exports single sheets. Excel automatically handles date and number formatting based on your system locale. Choose Excel when recipients primarily use Microsoft Office or when you need better formatting preservation than CSV provides.

Exporting view to Excel format

JSON and XML

Both JSON and XML create structured data files for programmatic use. JSON is more concise and works better with web applications and modern APIs. XML provides hierarchical structure and may be required by enterprise systems or legacy integrations. Choose these formats when exporting for developers, API integration, or systems that specifically require structured data rather than spreadsheet formats.

Export files (grouped by row)

The “Export files” option creates a downloadable archive containing all files and images from file fields in your view, organized by row ID. Each row gets its own folder, making it easy to see which files belong to which records. This is particularly useful when you need to extract attachments, images, or documents from your table for offline use, archival purposes, or sharing with people who don’t need the structured data, just the files themselves.

What gets exported from views

Included in view exports: All visible field values in rows that pass current filters, field names as column headers (unless disabled), row order based on active sorts, and data formatted according to field types.

Excluded from view exports: Hidden fields don’t appear even if they contain data, filtered-out rows are completely omitted, row comments and mentions aren’t included, and row revision history stays in Baserow. Formula fields export their calculated values as static data, not the formulas themselves.

View-specific considerations: Personal views export only for the user who created them, since other users can’t access personal view configurations. Collaborative views can be exported by anyone with appropriate table permissions. View colors and conditional formatting don’t export; only the underlying data values.

Frequently asked questions

Why can’t I export my Kanban or Calendar view?

View export is currently limited to Grid views only. To export data from Kanban, Calendar, Gallery, or Timeline views, switch to a Grid view first or use the table export option, which works regardless of the current view type. The exported data will be the same; only the export access point differs.

Do exported views include hidden fields?

No, hidden fields are excluded from view exports. If you’ve hidden fields for privacy or simplicity, they won’t appear in exported files. To include all fields, create a view with all fields visible or use table export instead of view export.

Can I export multiple views at once?

No, Baserow exports one view at a time. To export multiple views from the same table, repeat the export process for each view. Each export produces a separate file with that view’s specific configuration.

What happens if I modify the view after starting an export?

Exports capture the view state at the moment you click “Export.” Changes made to filters, sorts, or field visibility after initiating export don’t affect the download. The exported file reflects the view configuration that existed when export began.

How do I create consistent recurring exports?

Create a dedicated view configured specifically for your recurring export needs with appropriate filters, sorts, and field visibility. Name it clearly (e.g., “Monthly Report Export”) and use this same view each time. The consistent view configuration ensures your exports maintain the same structure and formatting across reporting periods.

Can I export just the files without the data?

Yes, use the “Export files” option, which creates a zip archive containing only files from file fields, organized into folders by row ID. This gives you all the uploaded files, images, and attachments without the structured table data. The folder structure helps you identify which files came from which records.

Export and import

View configuration

View types

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.