How to create a number input

How to create a number input

There are situations, in which you want the user to be able to type only numbers into a form field because a non-numeric value does not make sense in the specific use case. Let’s see how to do it.

When it comes to input fields, Flutter knows nothing else but text (TextField or TextFormField). This makes sense because on a data type level, everything you can input is a text.

If you know that your text is of a specific format, you might want to prevent the user to enter something invalid so that you don’t have to validate every possible case of an invalid text.

Changing the keyboard

The first part of the solution has a very pragmatic underlying logic: if the user’s keyboard does not provide the possibility of entering an invalid character, it prevents him from entering one. This also has a usability aspect: if there is a default keyboard where 95 % of the provided keys are unused because the expected input is only numeric, then the user feels uncomfortable. Also, the really important keys (number keys) don’t take much space on the screen which makes them harder to be hit.

For this case, the TextField and the TextFormField both provide a property called keyboardType. This optional constructor argument expects a TextInputType. There are numerous constructors (mostly hidden behind a static const value that internally call the _ constuctor) for different keyboard types, such as:

  • text
  • multiline
  • number
  • phone
  • datetime
  • emailaddress
  • url
  • visiblePassword
  • name
  • streetAddress

If we want to use a number input without decimals, we can just go for number:

2  ...
3  keyboardType: TextInputType.number,

However, if we want to allow numbers with decimals, we need to use the named constructor numberWithOptions instead. This allows us to specify whether decimals are possible and whether signed numbers are possible.

2  ...
3  keyboardType: TextInputType.numberWithOptions(decimal: true),

The two options decimal and signed default to false. So if we use numberWithOptions without any argument, we get the same result as using TextInputType.number.

One important thing to note here, though: the number keyboard on iOS does not have a done button. If you need to have that, you will not get around using either the usual keyboard and a custom validation or one of the available third party plugins, as stated here.

Formatting the input

Specifying a certain keyboard might prevent the user from entering invalid input. However, the input could still come from other sources such as the clipboard: having copied invalid characters such as alphanumerical characters and pasting them into the field is not what this parameter stops the user from.

That’s what the inputFormatters property is for. InputFormatters are basically functions that are called whenever text is being typed, cut, copied or pasted e. g. in a TextField. The input is the text inside the field and the output is also text. That enables the InputFormatter to override the text based on what it’s inside.

This way we can replace parts of the text we don’t want to have with empty String ('').

There is a predefined TextInputFormatter for this exact purpose. It’s called FilteringTextInputFormatter. The caller can provide either a pattern that matches the allowed or the denied characters (via regular expression).

Because we know exactly what type of characters we want to allow (numbers), it’s much easier for us to define the allow filter instead of the deny filter:

1inputFormatters: <TextInputFormatter>[
2  FilteringTextInputFormatter.allow(RegExp(r'[0-9]')),

The regular expression matches every digit between 0 and 9. Using \d (for “digit”) would have the same effect.

If we want the Formatter to accept decimals as well, we use a custom TextInputFormatter. We can either define a separate class that extends the TextInputFormatter or we take the shortcut because we have a rather simple one and use the named constructor that lets us define the behavior in just one function:

1keyboardType: TextInputType.numberWithOptions(decimal: allowDecimal),
2inputFormatters: <TextInputFormatter>[
3  FilteringTextInputFormatter.allow(RegExp(r'[0-9]+[,.]{0,1}[0-9]*')),
4  TextInputFormatter.withFunction(
5    (oldValue, newValue) => newValue.copyWith(
6      text: newValue.text.replaceAll('.', ','),
7    ),
8  ),

TextInputFormatters can be chained. This means that within the list of input formatters the order matters. The output of the first formatter is taken as the input for the second and so on.

In our case, we want the first formatter to only allow a pattern with at least one digit [0-9]+ followed by either a dot, a comma or nothing [,.]{0,1} followed by at least zero digits [0-9]*.

Now we know that the output of this formatter is always of the mentioned format. Then we define a second formatter that replaces every occurrence of . by ,. This way, we have a normalized input, which we could easily make further use of. It doesn’t matter if the user enters a . or a , – it will always be transformed to a ..

Putting it all together

If we puzzle the pieces together to a reusable widget, the code could look something like this:

 1import 'package:flutter/material.dart';
 2import 'package:flutter/services.dart';
 4class NumberInput extends StatelessWidget {
 5  NumberInput({
 6    required this.label,
 7    this.controller,
 8    this.value,
 9    this.onChanged,
10    this.error,
11    this.icon,
12    this.allowDecimal = false,
13  });
15  final TextEditingController? controller;
16  final String? value;
17  final String label;
18  final Function? onChanged;
19  final String? error;
20  final Widget? icon;
21  final bool allowDecimal;
23  @override
24  Widget build(BuildContext context) {
25    return TextFormField(
26      controller: controller,
27      initialValue: value,
28      onChanged: onChanged as void Function(String)?,
29      readOnly: disabled,
30      keyboardType: TextInputType.numberWithOptions(decimal: allowDecimal),
31      inputFormatters: <TextInputFormatter>[
32        FilteringTextInputFormatter.allow(RegExp(_getRegexString())),
33        TextInputFormatter.withFunction(
34          (oldValue, newValue) => newValue.copyWith(
35            text: newValue.text.replaceAll('.', ','),
36          ),
37        ),
38      ],
39      decoration: InputDecoration(
40        label: Text(label),
41        errorText: error,
42        icon: icon,
43      ),
44    );
45  }
47  String _getRegexString() =>
48      allowDecimal ? r'[0-9]+[,.]{0,1}[0-9]*' : r'[0-9]';

Styling the decimals

We could even go a step further and style the decimals, making the separation more obvious for the observer. For this purpose we use the findings of this article about partially styling a TextField.

 1TextEditingController controller = StyleableTextFieldController(
 2  styles: TextPartStyleDefinitions(
 3    definitionList: <TextPartStyleDefinition>[
 4      TextPartStyleDefinition(
 5        style: const TextStyle(
 6          color: Colors.black38,
 7        ),
 8        pattern: r',(\d+)$',
 9      )
10    ],
11  ),

We want the part after the decimal to be grayed out a little bit so we apply a respective TextStyle to the part of the text that matches the regular expression: ,(\d+)$.


Flutter does not provide a predefined input for numbers. However, we can use the capabilities of a TextField (or TextFormField) to mimic the behavior we want a number input to have.

It’s as simple as changing the keyboard to one that only provides numbers and the allowed characters to digits only.

If we want to support decimals as well, we can give the named constructor of TextInputType a respective argument. We can user TextInputFormatters to disallow certain characters and normalize the decimal separator.

Comments (1) ✍️


“Now we know that the output of this formatter is always of the mentioned format. Then we define a second formatter that replaces every occurrence of . by ,. This way, we have a normalized input, which we could easily make further use of. It doesn’t matter if the user enters a . or a , – it will always be transformed to a ..”

The first and second sentence contradict each other: either the period is replacing the comma or the comma is replacing the period. You need to decide.

Reply to Tom

Comment this 🤌

You are replying to 's commentRemove reference