- The row cap people search for doesn't exist in the docs
- Block limits and request caps, side by side
- Where this limit is enforced
- What happens when the workspace reaches 1,000
- Lifetime means deleting rows won't help
- Request limits that can look like a row cap
- My verdict for a growing workspace
- Frequently asked questions
Notion's developer docs state no maximum number of rows in a database. What they do state is a limit of 1,000 lifetime blocks for Free workspaces with more than one member, and every page, including each database row, is a block. Workspaces on higher plans and single-member Free workspaces have unlimited blocks.
The row cap people search for doesn't exist in the docs
If you've heard that a Notion database tops out at some number of rows, I'd treat that with caution. Notion's API documentation lists size limits for requests and for property values, but it doesn't state any maximum row count for a database. So I won't give you one either.
What the developer docs do describe is a block limit, and that's the number that can stop you adding rows. In Notion, a page is a block, and each row in a database is a page. That's why a block limit can feel exactly like a row limit when you hit it.
Block limits and request caps, side by side
These are the limits in Notion's developer documentation, as of Nov 2026 for the Free workspace lines.
| Item | Limit | Applies to |
|---|---|---|
| Lifetime blocks | 1,000 | Free workspaces with more than one member |
| Lifetime blocks | Unlimited | Higher plans and single-member Free workspaces |
| Grace period after the limit is first reached | Three days | Free workspaces |
| Block elements per request | 1000 | One API request |
| Payload size | 500KB | One API request |
| Related pages added per request | 100 | Relation property, one request |
Guests don't count as members, so a solo owner who shares pages with clients as guests is still a single-member workspace for this purpose. The limit is shared across the whole workspace, not handed out per connection.
Where this limit is enforced
This limit sits in the developer documentation, and it's worth reading it that way. The block-limit page describes enforcement for internal connections and OAuth connections to selected workspaces, not for personal access tokens. It doesn't describe how the same limit shows up when you're typing rows in the app, so I won't stretch it to cover that.
In practice, that means the people most likely to run into it are those using an integration or automation to push rows into a shared Free workspace, such as a form tool, a sync or a script.
What happens when the workspace reaches 1,000
The behaviour is more forgiving than a hard stop, at least at first.
- The write that first reaches the limit succeeds, and a three-day grace period starts.
- During the grace period, things carry on as normal.
- Once grace expires, any request that creates blocks fails. Creating a page fails, because the page is a block, and creating a database fails too, because the database is a block.
- Reads, deletes and edits that don't create blocks still work, including title and property edits.
So your existing rows stay readable and editable. What stops is adding anything new.
Lifetime means deleting rows won't help
Notion developer docs on workspace block limits are explicit that the 1,000 limit counts lifetime blocks. Deleting blocks doesn't restore capacity. A Free multi-member workspace counts every page and database as a block, so clearing out old rows won't give you room for new ones. After the three-day grace period, anything that creates blocks fails, but edits and reads carry on.
That's the part that catches people out. The usual instinct when something's full is to tidy up, and here tidying up doesn't change the count.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Request limits that can look like a row cap
A couple of request-level numbers in the docs sometimes get mistaken for database caps. They aren't.
- A single API request is capped at 1000 block elements and 500KB. That limits how much you can send in one go, not how big the database can grow.
- A relation property can hold far more than 100 related pages. 100 is only how many you can add or set in a single request.
- A multi-select property accepts up to 100 options per request.
If an import or automation fails on a large batch, splitting it into smaller requests is usually the fix, rather than a sign the database is full.
My verdict for a growing workspace
Don't plan around a row limit, because the docs don't give one. Plan around blocks instead. If you're a team on a Free workspace pushing rows in through an integration, watch the 1,000 lifetime count and remember deleting won't help, so move up a tier before the grace period runs out. If you're setting up your first one, my guide on building a database in Notion covers the basics, and my wider look at how Notion databases work explains how rows and pages fit together. If you're comparing other tools, there's my roundup of Notion alternatives.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Is there a row limit in a Notion database?
Notion's docs state no maximum row count. The limit that applies is the block limit on Free multi-member workspaces.
How many blocks does a Free workspace get?
1,000 lifetime blocks for Free workspaces with more than one member. Single-member Free workspaces have unlimited blocks.
Does deleting rows free up space?
No. Deleting blocks doesn't restore capacity.
What happens when the limit is reached?
The write that reaches it succeeds and starts a three-day grace period. Afterwards, anything that creates blocks fails, while reads and edits still work.
Do guests count?
No. Guests don't count as members for this limit.
