Baserow databases make it easy to organize complex information without needing technical expertise or coding skills.
Understand how Baserow databases organize your data using tables, fields, and rows. Learn the core concepts, see practical examples, and discover how databases fit into your workspace structure.
A database is a structured collection of tables containing rows (records) and columns (fields).
A Baserow database is a collection of related tables that store and organize your data. Unlike traditional spreadsheets, Baserow databases let you create relationships between tables, automate workflows, and build custom applications on top of your data.
Databases belong to workspaces. Each database lives inside a workspace and can contain multiple tables for different aspects of your projects, like customer information, inventory tracking, or project management.
Before creating a database, you need a workspace. Workspaces are the top-level organizational unit where you manage team members, permissions, and billing.
Workspace
└── Database
├── Table 1 (Customers)
│ ├── Row 1 (Customer A)
│ ├── Row 2 (Customer B)
│ └── Fields (Name, Email, Phone...)
├── Table 2 (Orders)
└── Table 3 (Products)
Databases contain multiple tables. Each database can hold unlimited tables. For example, a “Sales Management” database might include: Customers table, Orders table, Products table, and Invoices table.
Tables organize different types of information, and consist of:
Fields define data types. Baserow offers 25+ field types to structure your data properly: Text fields (single line, long text), Number and currency fields, Date and time fields, Links to other tables, File and image uploads, Formulas and calculations, and many more.

| Feature | Traditional spreadsheets | Baserow databases |
|---|---|---|
| Data relationships | Manual cross-referencing | Built-in table linking |
| Field types | Generic text/numbers | 25+ specialized field types |
| Multiple views | One sheet view | Grid, Gallery, Kanban, Calendar, Timeline |
| Collaboration | File sharing conflicts | Real-time multi-user editing |
| Automation | Complex macros required | Visual webhooks and API integration |
| File storage | Embedded with size limits | Dedicated file fields with proper storage |
| Access control | Share entire file | Granular permissions per table/view |
| Applications | Not possible | Build custom apps with Application Builder |
Database names can be updated anytime without affecting data or structure:
⋮ icon next to the database nameUse clear, descriptive names (e.g., “2024 Sales Pipeline”), include project codes or team names, keep names under 50 characters, and avoid special characters that may cause API issues.
Currently, databases cannot be moved between workspaces directly. To transfer a database:
Alternatively, duplicate the database, then manually recreate it in the new workspace for complex structures.
Baserow simplifies database integration without requiring developer expertise:
For non-technical users:
For developers:
There’s no hard limit on the number of databases per workspace. You can create as many as needed to organize different projects or departments. However, consider keeping related tables in the same database for easier relationship management and better organization.
A database is a container that holds multiple related tables. A table is where your actual data lives in rows and columns. For example, a “Sales” database might contain “Customers,” “Orders,” and “Products” tables.
Not directly at the database level, but you can create public views that show specific data from a single table. You can also use role-based permissions to control which tables workspace members can access. For true table-level isolation, consider using separate databases.
Export your database through the workspace settings menu. Choose between exporting individual tables as CSV files or the entire database structure. For automatic backups, you can also use the API to create automated snapshots as backup.
Yes! Simply create a new table and import your Excel file. After import, you can refine field types and add Baserow-specific features like relationships and formulas. Learn more: How to transform spreadsheets into databases.
Baserow databases are designed to scale efficiently. Performance depends on your hosting plan, but typical databases can handle hundreds of thousands of rows. Use filters and views to work with subsets of data, and consider archiving old records to maintain performance. Enterprise plans offer enhanced performance for very large datasets.
Now that you understand Baserow databases, explore these topics:
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.