# Inserting macros

The suite ships roughly sixty-one macros across every capability. In a suite install their titles drop the word macro, so the picker reads "Diagram (Capable)" rather than "Diagram macro (Capable)".

There are three ways to insert one, and the right one depends on whether you know what you are looking for.

---

## Three ways in

![The Capable menu open beneath a page title, listing Approval, Calendar, Diagrams, Images, Number headings, Macros, Github, Markdown and Publishing, with Macros highlighted and described as add macros ](https://help.gocapable.com/images/c9ea1d79-10ab-4ee0-98a7-46510f9b3e0d.webp)

Macros has its own entry in the Capable menu under the page title, which opens the picker without going through the editor.

![The Capable macro picker with a category list on the left including Layout, Cards and Footnote, a preview of three fruit cards in the middle, and card configuration and column settings on the right.](https://help.gocapable.com/images/cdd6f74c-6ae3-4878-aea6-dcbe559f4103.webp)

Capable's own picker groups the macros by category and previews the result while it is being configured, then inserts it where you choose.

| **Route**             | **Best for**                                   |
| --------------------- | ---------------------------------------------- |
| The '+' macro browser | Browsing when you are not sure what exists     |
| The Capable byline    | Reaching a capability from the page you are on |
| Capable Studio        | Building something from a starting point       |

ℹ️

**The Search table macro is suite-only.** It is filtered out of Capable's macro browser in every non-suite app, because it depends on columns contributed by the other capabilities.

---

## Two macros worth knowing about

* **Site metadata** sets the SEO title, description and slug for a page published through Sites. Suite only.
* **Word Count** reports paragraphs, words and characters, and feeds the same values into Confluence search.

---

## When a macro is missing

A macro that is not in the picker is usually a hidden capability. Hiding a capability removes it from the Capable navigation and byline, but note the caveat below.

---

## A few things worth knowing

* Hiding a capability is a visibility change, not a functional one: the macros stay in Confluence's own '/' insert menu, and existing macros on pages keep rendering.
* Macro names differ slightly between the suite and standalone apps, which matters when following documentation written for the other one.
* The macro picker is shorter if you hide the capabilities you do not use.

---

## Related

[Page toolsThe capabilities with no macro.](https://help.gocapable.com/capable/page-tools.html)

[CapabilitiesWhat each macro belongs to.](https://help.gocapable.com/capable/capabilities.html)

[AdministrationHiding what you do not need.](https://help.gocapable.com/capable/administration.html)

---

_Sixty-one macros. One install._