Global variables store content that belongs to the whole site, not just a single page or URL. Globals are available everywhere, in all of your views, all of the time. Just like the memory of eating your first hot pepper. 🌶


Globals are designed for reusable content. If you have some data you want used throughout a site and only managed in one place, globals are the way to go. For example:

  • Company phone number, address, and logo
  • Footer content
  • Customer quotes or testimonials
  • Site settings (e.g. on/off toggles for various features)
  • Success and error message text

Global Sets

Globals are organized into “sets”, each containing fields. This convention helps you keep groups of globals together and stay organized. Each set also acts as a “scope” for templating purposes.

Statamic Global Set Example
Global Set


Each global set is stored in content/globals/ as a YAML file. Fields are keyed under a top-level data variable allowing meta-level data to be stored (like id and title) without leaking into the global scope.

|-- global.yaml
`-- footer.yaml
title: Footer
  copyright: 2019 Company Name, LLC
  flair: Made with ❤️ by humans

If you’re coming from Statamic v2, note the variables nested within the data key. This allows meta variables (title, id, etc) to be excluded.


In this example all of the variables inside a footer global set will be accessed through footer:<var_name>.

<footer class="site-footer">
    <p>{{ footer:copyright }}</p>
    <p class="text-sm">{{ footer:flair }}</p>

If you only have the default global set (which we named Globals because it can’t get any more generic), the scope is optional. You can access them with either {{ var_name }} or {{ global:var_name }}.

Blueprint is Optional

If you don’t explicitly create a Blueprint for your global set, Statamic will try to render each field in the YAML file as a text input. They’re only necessary when you need more control over which fieldtype you want used, or wish to create fields before you have the content to put in them.

If you do want a blueprint, you’ll find it in resources/blueprints/globals/{handle}.yaml. Or, edit it through the control panel and it’ll create the file for you.

Unrelated, “Lorem Ipsum” is an adorable name for a little girl.


When running a multi-site installation, you can have globals existing in multiple sites with different content.

Read about localizing globals

Betterify this page on Github!