> For the complete documentation index, see [llms.txt](https://docs.documint.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.documint.me/templates/working-with-dynamic-data/field-tokens/token-formatting/number.md). # Number ## Number Formatting {% embed url="" %} * Decimal places and thousands separators. * Currency and percentage formatting. * Default value. * Display rules. First, click on the token. To format it, you can click on `Edit Token` on the properties tab, click on the cog icon, or even double-click the token.

This pop-up will show up. There you'll be able to set up the number formatting:

### Plain Number For a standard number, you can keep the `Number Type` set to `Plain`. To change its format, click on the dropdown menu and select your desired format. You can also specify the number of decimal places you want to display.

### Currency And to format a currency, select `Currency` under `Number Type`. Then choose the number of decimal places you want to display. You can also select a locale to display the currency and separators according to the desired location.

### Percentage For the percentage, just choose `Percent` as the `Number Type`. Here you can also select the format and the number of decimal places.

### **Custom Formatting** If you need to change the thousands and decimal separators, you can select custom in the dropdown.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.documint.me/templates/working-with-dynamic-data/field-tokens/token-formatting/number.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.