wppaste
WordPress

is_page_template( string|string[] $template = '' ): bool

Since
2.5.0, 4.2.0, 4.7.0
Source
wp-includes/post-template.php:1812
Determines whether the current post uses a page template.

Description

This template tag allows you to determine if you are in a page template.
You can optionally provide a template filename or array of template filenames and then the check will be specific to that template.

For more information on this and similar theme functions, check out the https://developer.wordpress.org/themes/basics/conditional-tags/ Conditional Tags article in the Theme Developer Handbook.

Compatibility

WordPress
since 4.7.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$templatestring|string[]optional
The specific template filename or array of templates to match.Default: ''

Return value

bool
True on success, false on failure.

Performance profile

How much work a call to is_page_template() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Heavy

Reaches the database via get_post().

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
5–27

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 32.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
7

7 places in core call this, so the cost is paid more often than your own code shows.

What it touches

  • querycontent queryget_post()one call below is_page_template()

Further down the call graph this can also reach hook, cache, serialize, option and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 2 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost is_page_template() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
!is_singular()5is_singular()
is_singular()14–27is_singular(), get_queried_object_id(), get_page_template_slug()

Across PHP versions

PHPCompiledExecutedBranchesNotes
8.6-dev325–278
8.5325–278
8.4325–2786 fewer instructions than PHP 8.3
8.3385–338
8.2385–338
8.1385–338
7.4385–338

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Uses · 3

Used by · 7

Source code

function is_page_template( $template = '' ) {	if ( ! is_singular() ) {		return false;	} 	$page_template = get_page_template_slug( get_queried_object_id() ); 	if ( empty( $template ) ) {		return (bool) $page_template;	} 	if ( $template === $page_template ) {		return true;	} 	if ( is_array( $template ) ) {		if ( ( in_array( 'default', $template, true ) && ! $page_template )			|| in_array( $page_template, $template, true )		) {			return true;		}	} 	return ( 'default' === $template && ! $page_template );}

Changelog

Introduced in 2.5.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

4.7.0
Now works with any post type, not just pages.from the docblock
4.2.0
The $template parameter was changed to also accept an array of page templates.from the docblock
2.5.0
Introduced.from the docblock

About this page

Parsed data
Generated from the wordpress-develop 6.7.7 tag, from src/wp-includes/post-template.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.