Native Notion forms don’t have a minimum or maximum setting for number questions. A number question is just the Number property, and Notion documents no range limit for it. You can flag out-of-range answers after they arrive with a formula, offer fixed choices instead, or use a form tool that checks the range before the respondent can submit.
Does a Notion form support number min and max?
A Notion form number min max setting isn’t something Notion documents. The forms help page says the question type “is the equivalent of the property type,” and its only answer rules are Required and a maximum number of selections for multi-select, relation and people questions.
The Number property has nothing either. Notion’s property guide says it “accepts numbers” and can be shown as currency or a progress bar. There’s no range field. Through the API, a number value is simply “a JSON number or null,” so {"Estimate": {"number": 8}} is all a form sends.
Type any number into “How many guests?” and Notion saves it.
Your options, compared
The right fix depends on whether you need to block a bad number or just notice it.
| Goal | Option | Catches it | Cost |
|---|---|---|---|
| Notice odd answers | Formula flag + filtered view | After submit | Free, native |
| Avoid typing entirely | Select with fixed choices | Before submit | Only works for a short list |
| Block it at the form | Form tool with min/max | Before submit | Another tool |
| Trust the number | Check on your side | After submit | Manual review |
For small ranges, a select often beats a number field. A guest count from 1 to 10 works fine as ten options. The rating scale guide shows how to turn select answers back into numbers you can average.
Flag out-of-range numbers with a formula
A formula property can label every row whose number falls outside your range. Notion’s formulas page describes if() as returning the first value when the condition is true and the second otherwise, and the syntax reference lists <, > and or.
Say your form asks for a budget that should sit between 0 and 5000. Add a formula property called Range check:
if(or(Budget < 0, Budget > 5000), "Out of range", "")
Then:
- Create a view of the responses database.
- Filter it to rows where Range check is “Out of range.”
- Open that view when new responses arrive, and follow up with the person.
This is the native setup I’d use. It won’t stop a bad answer. It puts every one in a single view, and for an internal form that’s enough. Empty answers pass the check, so mark the question Required if a blank number is also a problem.
How min and max work in form tools
Form tools that write to Notion usually validate the range in the browser, the same way an HTML number field does. MDN’s number input reference says a value below min or above max “fails constraint validation,” so the form won’t submit until it’s fixed.
Two details catch people out:
- Decimals. The default step is 1, so only whole numbers count. Enter 1.1 and the field calls it invalid, even inside your range. A field for prices needs a step like
0.01, orany. - Typing past the arrows. The spin arrows stop at the limits. Typing doesn’t, and a typed value outside them is marked invalid rather than silently changed.
On phones, a number field also brings up a keyboard built for digits, which cuts typos before validation even runs.
Why a range check isn’t a security check
A browser range check stops honest mistakes, not determined people. MDN’s form validation guide warns that client-side validation “is too easy to bypass” and says plainly: “Never trust data passed to your server from the client.”
That’s fine for an internal form. For an expense reimbursement form or an order form, keep the formula flag even if your form tool checks the range, and review flagged rows before you pay or ship anything.
Can conditional logic enforce a range?
Native Notion logic can’t branch on a typed number. The forms help page says you can add conditional logic only “if your question is multiple choice,” and only on Business and Enterprise plans.
You can still route by range with a select. Ask “Budget band” with options like “Under 5000” and “5000 or more,” then show follow-up questions for the higher band. The conditional logic guide covers the setup.
Where nDBForms fits
nDBForms builds forms from your Notion database, and a Number property becomes a number question that writes straight into a new row. Respondents fill it in any browser without a Notion account.
Its conditional logic is on Pro and works with any Notion plan, so you can branch on a select band without upgrading Notion. The limitation: no form’s check can be trusted alone, this one included. Keep the Range check formula in Notion for any number that costs you money. For the other gaps in native forms, see the limitations of Notion forms.
FAQ
Can a native Notion form limit a number answer?
Not that Notion documents. A number question follows the Number property, and neither the forms help page nor the property docs list a minimum or maximum setting.
How do I catch out-of-range numbers in Notion?
Add a formula property that labels rows outside your range, then filter a view on that label. It catches bad answers after submission, not before.
Why does my form reject 1.1 when the range allows it?
A browser number field steps in whole numbers by default, so a decimal like 1.1 is invalid. The field needs a step such as 0.01 or any to accept decimals.
Is a min and max check enough to trust the value?
No. Browser-side checks are easy to bypass, so treat the number in Notion as a respondent’s claim and check anything that matters, like an amount you’ll pay out.
Can I use conditional logic to enforce a range?
Native Notion logic only works on multiple-choice questions, on Business and Enterprise plans, so it can’t branch on a typed number.