If you've been using Confluence for a while, you've probably come across these two popular macros for organizing content: tabs and expands.
And you've probably questioned at least once what the difference is between the two, or when you should actually use each. Which makes sense, at first glance, they can feel pretty similar, since both help you structure information and reduce clutter.
But having worked with both for a while, I can tell you they actually vary quite a bit in how they look and behave, and they each serve a very distinct purpose.
So in this article, I'll walk you through how the two macros differ, what to use them for, and some tips to get the most out of each.
You probably know this already, but most people don’t read Confluence pages top to bottom. They scan, jump around, and look for the part that’s relevant to them. If everything is laid out the same way with no structure, even well-written content becomes hard to use.
That’s why how you present content matters just as much as the content itself. Macros aren’t just "nice to have", they’re what make pages easier to read and navigate.
Tabs and expanders macros are two of the most useful tools for that. They just approach it differently.
Tabs are built for navigation. You use them when you're organizing content into categories and letting the reader choose which one to focus on, while the page itself stays the same length no matter how much content sits inside each section.
They work best when your content is split into distinct but equally important sections that belong together. They’re especially useful for comparisons, but also for showing steps in a sequence, such as onboarding flows, where users may want to move through information one stage at a time. Instead of stacking everything in one long page, tabs let people move between sections without losing context.
However, tabs aren’t available as a native macro in Confluence. So to use them, teams usually rely on third-party apps like Content Formatting Toolkit, which give you more flexibility in how tabs are set up and displayed, from different customization options to choosing between horizontal or vertical layouts depending on your page.
You’ll often see them used in product pages or onboarding flows, where each section focuses on a different aspect of the same topic.
For detailed step-by-step setup, check our dedicated tutorial video.
Tip: Trying to fit too much into each tab makes them harder to use. If a tab turns into a long scroll, you’re just moving the problem inside the section. In that case, it’s usually better to split content into a child page. Also, if you have more than 5 tabs, switching to a vertical layout tends to work better.
Collapsible sections (or expanders) solve a different problem. Rather than switching between sections, they let you control what's visible upfront and what can stay out of the way until someone actually needs it. All section titles remain visible, and readers can choose to open one, several, or none.
They're a good fit when your page includes supporting details that would interrupt the main flow if it were always visible, like FAQs, troubleshooting steps, or technical notes.
There are two methods to add expanders to your Confluence page:
The native Expand macro is the Confluence built-in option. It’s quick to use and works well for basic content. You add a title, place your content inside, and let users reveal it when needed. For short or straightforward pages, that’s often enough. But, you can only insert one expander at a time. Where it starts to feel limited is on more complex pages. Styling is minimal, sections can blend in easily, and you’re restricted in what you can include inside (you can’t nest other bodied macros).
They work best for when you need more structure or visibility, thanks to their advanced customization options. You’re not adding expanders one by one like the native macro, you’re building them inside a single container, which gives you a more consistent layout across the page.
You also get more flexibility in how they’re displayed (vertical or horizontal), along with styling options that make sections easier to scan and distinguish along the page.
For detailed step-by-step setup, check the dedicated tutorial video.
Tip: With expanders, the most common mistake is hiding important information. If something is essential, it shouldn’t sit behind a click. Titles also matter more than anywhere else here, they’re what people rely on to decide what to open.
At a glance, they can feel interchangeable. In practice, they shape the page in very different ways. Let’s break it down:
→ Tabs answer the question: "which section do I want?". You can quickly move back and forth between sections and deliberately choose one view to focus on at a time. This is especially helpful when content is balanced across sections.
→ Expanders, on the other hand, answer the question:"do I need more details here?". They let you layer information for more depth while keeping the page readable. You can fit longer content and still control how much of it is visible at a time.
Here's a side-by-side to make it easier to compare:
|
Aspect |
Tabs |
Expanders |
|
Layout |
Fixed layout, one section visible at a time. Page length stays stable |
Flexible layout, multiple sections can be open at once. Page grows as you expand content. |
|
Purpose |
Organize content into separate, parallel sections. |
Hide or reveal additional detail within the same flow. |
|
User Interaction |
Switch between sections quickly. |
Scan first, then open only what’s relevant. |
|
Best for |
Product pages, onboarding steps, dashboards |
FAQs, troubleshooting, technical details |
|
Content Visibility |
One section always displayed |
Users can choose to open none, one, or many |
At the end of the day, it’s not really about choosing tabs or expanders. It’s about understanding your content, your audience, and what you want people to do with the information once they land on your page.
Are they exploring? Comparing? Looking for a quick answer?
The clearer you are on that, the easier it becomes to pick the right structure, and build pages that people actually use, not just scroll through.
Mariem Daghbouji _Vectors_
0 comments