Counts through pages, elements, and more.

With the counter function, you can access and modify counters for pages, headings, figures, and more. Moreover, you can define custom counters for other things you want to count.

Displaying a counter

To display the current value of the heading counter, you call the counter function with the key set to heading and then call the display method on the counter. To see any output, you also have to enable heading numbering.

The display method optionally takes an argument telling it how to format the counter. This can be a numbering pattern or a function.

#set heading(numbering: "1.")

= Introduction
Some text here.

= Background
The current value is:

Or in roman numerals:

Modifying a counter

To modify a counter, you can use the step and update methods:

The heading counter is stepped before the heading is displayed, so Analysis gets the number seven even though the counter is at six after the second update.

#set heading(numbering: "1.")

= Introduction

= Background
#counter(heading).update(n => n * 2)

= Analysis
Let's skip 7.1.
#counter(heading).step(level: 2)

== Analysis
Still at #counter(heading).display().

To define your own counter, call the counter function with a string as a key. This key identifies the counter globally.

#let mine = counter("mycounter")
#mine.display() \
#mine.display() \
#mine.update(c => c * 3)
#mine.display() \

How to step

When you define and use a custom counter, in general, you should first step the counter and then display it. This way, the stepping behaviour of a counter can depend on the element it is stepped for. If you were writing a counter for, let's say, theorems, your theorem's definition would thus first include the counter step and only then display the counter and the theorem's contents.

#let c = counter("theorem")
#let theorem(it) = block[
  *Theorem #c.display():* #it

#theorem[$1 = 1$]
#theorem[$2 < 3$]

The rationale behind this is best explained on the example of the heading counter: An update to the heading counter depends on the heading's level. By stepping directly before the heading, we can correctly step from 1 to 1.1 when encountering a level 2 heading. If we were to step after the heading, we wouldn't know what to step to.

Because counters should always be stepped before the elements they count, they always start at zero. This way, they are at one for the first display (which happens after the first step).

Page counter

The page counter is special. It is automatically stepped at each pagebreak. But like other counters, you can also step it manually. For example, you could have Roman page numbers for your preface, then switch to Arabic page numbers for your main content and reset the page counter to one.

#set page(numbering: "(i)")

= Preface
The preface is numbered with
roman numerals.

#set page(numbering: "1 / 1")

= Main text
Here, the counter is reset to one.
We also display both the current
page and total number of pages in
Arabic numbers.
Preview Preview

Time travel

Counters can travel through time! You can find out the final value of the counter before it is reached and even determine what the value was at any particular location in the document.

#let mine = counter("mycounter")

= Values
#locate(loc => {
  let start-val = mine.at(loc)
  let elements = query(<intro>, loc)
  let intro-val = mine.at(
  let final-val = mine.final(loc)
  [Starts as: #start-val \
   Value at intro is: #intro-val \
   Final value is: #final-val \ ]

#mine.update(n => n + 3)

= Introduction <intro>


Let's dissect what happens in the example above:

Other kinds of state

The counter type is closely related to state type. Read its documentation for more details on state management in Typst and why it doesn't just use normal variables for counters.

Question mark

Create a new counter identified by a key.

str or label or selector or function
Question mark

The key that identifies this counter.

Question mark


Displays the current value of the counter.

self.display() -> content

none or str or function
Question mark

A numbering pattern or a function, which specifies how to display the counter. If given a function, that function receives each number of the counter as a separate argument. If the amount of numbers varies, e.g. for the heading argument, you can use an argument sink.

If this is omitted, displays the counter with the numbering style for the counted element or with the pattern "1.1" if no such style exists.

Default: none


If enabled, displays the current and final top-level count together. Both can be styled through a single numbering pattern. This is used by the page numbering property to display the current and total number of pages when a pattern like "1 / 1" is given.

Default: false


Increases the value of the counter by one.

The update will be in effect at the position where the returned content is inserted into the document. If you don't put the output into the document, nothing happens! This would be the case, for example, if you write let _ = counter(page).step(). Counter updates are always applied in layout order and in that case, Typst wouldn't know when to step the counter.

self.step() -> content


The depth at which to step the counter. Defaults to 1.

Default: 1


Updates the value of the counter.

Just like with step, the update only occurs if you put the resulting content into the document.

) -> content

int or array or function or counter-update
Question mark

If given an integer or array of integers, sets the counter to that value. If given a function, that function receives the previous counter value (with each number as a separate argument) and has to return the new value (integer or array).


Gets the value of the counter at the given location. Always returns an array of integers, even if the counter has just one number.

self.at() -> intarray

Question mark

The location at which the counter value should be retrieved. A suitable location can be retrieved from locate or query.


Gets the value of the counter at the end of the document. Always returns an array of integers, even if the counter has just one number.

self.final() -> intarray

Question mark

Can be an arbitrary location, as its value is irrelevant for the method's return value. Why is it required then? Typst has to evaluate parts of your code multiple times to determine all counter values. By only allowing this method within locate calls, the amount of code that can depend on the method's result is reduced. If you could call final directly at the top level of a module, the evaluation of the whole module and its exports could depend on the counter's value.