# What are Metaobjects?

This page will explain what **Metaobjects** are, how they differ from Metafields, and how to use them most effectively.

**Metaobjects** are a great way to store and manage data that does not belong directly to any pre-existing scope but is instead self-sufficient and has meaning by itself. You can think of one **Metaobject** definition as a standalone scope that can function by itself. An example of a standalone scope would be products or pages. Each one of these scopes contains information that is organised neatly into a template. For products that would be: Product title, description, media, price, inventory, and all the additional data you may have attached to them using Metafields.

**Metaobjects** come into play when you need to create self-sufficient groups of information that fit neatly into templates. To illustrate our point, we will give you a practical example of **Authors**.

Let's say you run a book store and want to organise all your authors properly, or you have an extensive blog on your store that is run by multiple people and you want to avoid having to write out all of the information about the author every time you publish a blog or add a new book. The ideal way to organise this data is by using **Metaobjects**. This would provide you with a convenient template you can use to add new, or easily edit and manage your authors.

Some of you probably thought about an approach to solve this using Metafields. Metafields are a powerful tool to attach data to pre-existing structures like products (books in our case) or blogs. Creating the author template on products using Metafields would look something like this:

<figure><img src="/files/GGONctWyyj8H6rZVNh0X" alt=""><figcaption></figcaption></figure>

It would work, but it would lead to the author data being bound to its book which would result in you having to add all the author data again every time you add a new book (or blog post). Luckily Metafields can also reference **Metaobjects**, so you can have the best of both worlds - the superior data organisation of **Metaobjects**, and the specificity of Metafields.

<figure><img src="/files/4OR1vepysvRXalAvTGtu" alt=""><figcaption></figcaption></figure>

With **Metaobjects**, we can approach this by grouping  4 fields we had into one template, and every time we want to add a new author we can do so by pumping out another **Metaobject** instance. This way, adding a book whose author is already created is as easy as pointing. Also if you wanted to display the author itself this approach enables that as well, while that would be hard to do taking the other route. Editing an author’s data is also made easier this way since you can edit it in one place and it would update everywhere instead of having to go through all the author’s books and editing each one.

As you can see this fundamentally changes the position of the author. Instead of being bound to a book it is an entity that functions by itself. This is the moment when **Metaobjects** shine the brightest.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.accentuate.io/metaobjects/what-are-metaobjects.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.