Globals (Statamic)

Globals in Statamic are sets of variables that are available across every page of your site without needing to query or pass them explicitly. They’re defined through the Control Panel, backed by blueprints just like entries, and stored as YAML files in content/globals/. Once defined, global values can be referenced in any Antlers or Blade template by their variable name.

A typical Globals setup might include site-wide content like a phone number, email address, physical address, social media URLs, and a default meta description. It might also include configuration-style values like whether a promotional banner is enabled, or labels used in the site header and footer.

WordPress Equivalent: Options Pages

The closest equivalent in WordPress is the Options Pages feature from Advanced Custom Fields (ACF) Pro, which lets you register admin pages where editors can manage site-wide settings. WordPress itself has a limited built-in options system (get_option() / update_option()), and the Customizer also serves a similar role for some sites, but ACF Options Pages became the standard approach for storing arbitrary structured data at the site level.

When migrating a WordPress site that uses ACF Options Pages, the content stored there maps naturally to Statamic Globals. The migration process involves identifying what’s stored in each Options Page, creating a matching Global set in Statamic with an equivalent blueprint, and importing the values.

Organizing Globals

Statamic supports multiple Global sets, so you can organize site-wide data logically. A "Company Info" global might hold contact details and address. A "Social Media" global holds profile URLs. A "Site Settings" global holds feature flags and configuration. Each set gets its own admin page in the Control Panel and its own YAML file, which keeps things tidy as a site grows.

In templates, accessing a global is straightforward — if you have a global set called company with a field phone, it’s available as {{ company:phone }} in Antlers. The variable is available everywhere without any setup in the route or controller.

This is one of the small ergonomic differences that Statamic developers tend to appreciate: common site-wide data just works in templates without threading variables through every page request.