Notion forms are free on every plan, but they have real limits. The biggest are: conditional logic only exists on the Business and Enterprise plans, public web forms are always anonymous, file uploads cap at 5 MB per file on Free, and you can’t build or edit a form on mobile or on a linked database view. Most of the rest are smaller gaps in design control, exports and large response tables.
The limits at a glance
| Limit | Who it affects | Workaround |
|---|---|---|
| Conditional logic needs Business or Enterprise | Free and Plus workspaces | Upgrade, split into separate forms, or use an external form tool |
| Logic only on multiple-choice questions | Everyone with logic | Turn the branching question into a select |
| Web forms are always anonymous | Anyone collecting from outside the workspace | Add a required name or email question |
| Uploads up to 5 MB per file on Free | Free workspaces | Ask for a link instead of a file, or upgrade |
| No building or editing on mobile | People who work from a phone | Use desktop or web |
| Forms only on the original database | Teams that work in linked views | Add the form to the source database |
| Notion branding on public forms | Free workspaces | A paid plan removes it |
| Can’t export from the Form view | Anyone who needs a CSV | Export from a table view |
| Slow loading with very many responses | High-volume forms | Start a new form version or delete old responses |
| Template forms send answers to the original creator | Anyone who duplicates a template | Rebuild the form yourself |
1. Conditional logic is a Business feature
Notion added branching in its March 26, 2025 release: forms can now ask follow-up questions based on earlier answers, and “This feature is available on Business and Enterprise plans.” On the Notion pricing page, Plus is $10 per member per month and Business is $20, so a five-person team pays double for a “show this question only if” rule.
There’s a second catch in the Notion help center: logic only works on multiple-choice questions. To branch on a number (“show the enterprise questions if the team is large”), you first have to turn it into a set of choices.
Workaround on Free or Plus: keep the form short enough that everyone can see every question, or make two forms (one per path) and link to the right one from your page.
2. Public forms are always anonymous
Forms shared with anyone on the web are always anonymous, per the help center. You only see who answered on workspace-only forms with anonymous responses turned off. In exchange, people outside your organization can fill out a web form even without a Notion account, as the Notion forms guide confirms.
Say you send a feedback form to ten clients and three reply. Without a name question, you get three anonymous rows and no idea who found the invoice process confusing. Make “Your name” or “Your email” a required question from day one.
3. File uploads follow your plan
A files & media question uses your workspace’s upload limit. The pricing page lists “Up to 5 MB” per file on Free, and “~5GB max per file” on paid plans. Five megabytes is fine for a headshot or a one-page PDF. It’s not enough for a design portfolio, a long screen recording or a scanned contract with images.
If you’re on Free and expect large files, ask for a share link (Google Drive, Dropbox) as a URL question instead.
4. You can’t build forms on mobile
You build and edit forms in the desktop or web app only. Respondents can answer on a phone, but you can’t fix a typo in a question from the train.
Some forms can also only be completed while logged into the workspace that made them. Test a workspace-only form from a personal account and you’ll hit this.
5. Forms only live on the original database
The guide says “Forms are only available in the original database that contains the data source.” If your team works from a linked view of a “Requests” database on a project page, the Form option won’t appear there. Open the source database and add the form there. You also need Full access to that database, as covered in our step-by-step guide to creating a Notion form.
6. Design control is thin
Every question is a database property, and edits to questions sync to property names by default. On the submit screen you can set the button color and text, the confirmation title and body, and email copies of each answer. That’s about it. Free gets “Basic forms”. Plus gets “Custom forms” and can remove Notion branding, which only applies to forms shared on the web.
I couldn’t find three things anywhere in Notion’s form documentation: a redirect to your own page after submit, prefilling answers from URL parameters, and a cap on the number of responses. Need any of them? Plan for an external tool.
7. Question types are tied to properties
A question is a property, so the form can only ask what a property can store. The guide lists single-select, multi-select, text, date, person, files & media and number among the types. Long answers only work on text questions. You can cap how many options someone picks on multi-select, relation and people questions, but there’s no per-question validation like “must be a company email.”
8. Exports and big response tables
You can’t export a Form view. Responses land in a table view named Responses by default, and you export from there. The help center also warns that very high response volumes may load slowly. Its fix is to create a second version of the form or delete old responses, which turns an always-on lead form into a maintenance chore.
9. Admins and templates can break live forms
- Enterprise admins can switch off web publishing. The same setting blocks Notion Sites, and turning it on takes live web forms down.
- Duplicated template forms report to someone else. Notion warns that forms duplicated from a template must be rebuilt from scratch, or responses go to the original creator.
Guests can fill out a form only if they’ve been given access to the connected database.
Where the limits start to hurt
For internal forms (a bug report, a request queue, a weekly check-in), none of this matters. Notion’s form is free, sits next to your data and has nothing to break. Customer-facing forms are a different story. Anonymous answers, no branching on Free or Plus, and almost no control over the look are exactly what goes wrong on a client intake or job application form. Our overview of what Notion’s form builder can and can’t do covers whether the built-in builder is enough.
The usual fix is a separate form tool that writes each answer into the same Notion database. As of October 2026, nDBForms is one: it builds a form from your existing database, respondents don’t need a Notion account, and each submission becomes a new row. It has 17 question types, including file upload, Notion relation and Notion people. Conditional logic, multi-page forms and Google Drive uploads up to 10 MB per file are on Pro ($12/month founding price), and logic works on any Notion plan.
That route has costs. It’s one more tool in your stack, it keeps its own copy of each response, and its Free plan stops at 3 forms and 100 responses a month. Its upload cap is also smaller than a paid Notion plan’s, so for big files on a paid Notion workspace, native forms win. Our alternatives page compares the two approaches, and this job application form shows a finished build.
FAQ
Can Notion forms have conditional logic on the Free plan?
No. Notion says conditional logic is only available on the Business and Enterprise plans, and it only works on multiple-choice questions.
Why are my public Notion form responses anonymous?
Forms shared with anyone on the web are always anonymous. If you need to know who answered, add a required name or email question.
What is the file upload limit on a Notion form?
It follows your workspace plan. The Free plan allows uploads up to 5 MB per file; paid plans allow roughly 5GB per file.
Can I add a form to a linked database in Notion?
No. Forms only work in the original database that holds the data source. Open the source database and add the Form view there.
Can I export responses straight from a Notion form?
Not from the Form view. Switch to a table view, such as the default Responses view, and export from there.