ifeval Directive

Lines enclosed by an ifeval directive (i.e., between the ifeval and endif directives) are included if the expression inside the square brackets of the ifeval directive evaluates to true.

Example 1. ifeval example
ifeval::[{sectnumlevels} == 3]
If the `sectnumlevels` attribute has the value 3, this sentence is included.

The ifeval directive does not have a single-line or long-form variant like ifdef and ifndef.

Unlike ifdef and ifndef, you cannot terminate a specific ifeval directive using its complement. For example, the following ifeval block is not valid:

Example 2. Invalid ifeval terminator
conditional content

You can only terminate the previous ifeval directive using an anonymous endif::[] directive, as shown here:

Example 3. Valid ineval terminator
conditional content

If you’re mixing ifeval directives with ifdef or ifndef directives, you should always close multiline ifdef and ifndef directives by name (endif::name-of-attribute[]) so the ifeval directive does not end prematurely.


The expression of an ifeval directive consists of a left-hand value and a right-hand value with an operator in between. It’s customary to include a single space on either side of the operator.

Example 4. ifeval expression examples
ifeval::[2 > 1]

ifeval::["{backend}" == "html5"]

ifeval::[{sectnumlevels} == 3]

// the value of outfilesuffix includes a leading period (e.g., .html)
ifeval::["{docname}{outfilesuffix}" == "main.html"]


Each expression value can reference the name of zero or more AsciiDoc attributes using the attribute reference syntax (for example, {backend}).

Attribute references are resolved (i.e., substituted) first. Once attributes references have been resolved, each value is coerced to a recognized type.

When you expect the attribute reference to resolve to a string, that is, a sequence of characters, enclose that side of the expression in quotes. For example:

Example 5. ifeval that compares two string expressions
ifeval::["{backend}" == "html5"]

If you expect the attribute to resolve to a number, you do not need to enclose the expression in quotes. In this case, the values will be compared as numbers. The same rule applies to boolean values.

You should not attempt to mix value types in a comparison. For example, the following expression is not valid:

Example 6. Invalid ifeval expression
ifeval::["{sectnumlevels}" > 3]

The following values types are recognized:


Either an integer or floating-point value.

quoted string

Enclosed in either single (') or double (") quotes.


Literal value of true or false.

How value type coercion works

If a value is enclosed in quotes, the characters between the quotes is used and always coerced to a string.

If a value is not enclosed in quotes, it’s subject to the following type coercion rules:

  • an empty value becomes nil (aka null) (and thus safe for use in a comparison).

  • a value of true or false becomes a boolean value.

  • a value of only repeating whitespace becomes a single whitespace string.

  • a value containing a period becomes a floating-point number.

  • any other value is coerced to an integer value.


The value on each side is compared using the operator to derive an outcome.


Checks if the two values are equal.


Checks if the two values are not equal.


Checks whether the left-hand side is less than the right-hand side.


Checks whether the left-hand side is less than or equal to the right-hand side.


Checks whether the left-hand side is greater than the right-hand side.


Checks whether the left-hand side is greater than or equal to the right-hand side.

Both sides should be of the same value type. If they are not, the comparison will fail. If the comparison fails, the condition will evaluate to false (i.e., the content inside the directive will be skipped).

The operators follow the same rules as operators in Ruby.