Understanding Projects vs Graphics Packages

One of the most common points of confusion for new Flowics users is understanding the difference between a Project and a Graphics Package. This article explains how they relate to each other and when to use each.

The Hierarchy

Flowics organizes content in four levels:

Company 
└── Teams     
    └── Projects         
        └── Graphics Packages             
            └── Scenes & Overlays

Each level has a specific purpose. While not every workflow requires all levels, understanding the hierarchy will help you structure your work correctly from the start.

Projects

A Project is the top-level container for your work. It groups related Graphics Packages together and controls which team has access to them.

Think of a Project as a show or a client.

Examples

Morning News – Contains all packages for the morning show.
Election Night 2026 – Contains packages used for election coverage.
Sky News Australia – Contains all packages created for a specific client.

Key Things to Know About Projects

A Project belongs to a single Team.
Every Graphics Package must be created within a Project.
Projects can be set to Active or Inactive.
- Inactive Projects display a watermark on their outputs.
Only Company Admins and Team Admins can create Projects.

Graphics Packages

A Graphics Package is where your actual graphics live. It contains scenes, overlays, data connections, and outputs.

Think of a Graphics Package as a show rundown template—a specific set of graphics designed for a particular purpose.

Examples Within the Morning News Project

Lower Thirds – Name straps and lower-third graphics.
Fullscreens – Weather maps and fullscreen graphics.
Bugs & Tickers – Channel bugs, news tickers, and score bugs.

Key Things to Know About Graphics Packages

A single Project can contain multiple Graphics Packages.
Each Graphics Package has its own output URL.
Changes must be published before they become live.
Graphics Packages have a finite capacity, so avoid placing all graphics into a single package.

Project vs Graphics Package

Feature	Project	Graphics Package
Purpose	Organize content and manage access	Contain and output graphics
Created By	Company Admins or Team Admins	Editors and above
Contains	Graphics Packages	Scenes and Overlays
Has an Output URL?	No	Yes
Can Be Set Inactive?	Yes	No
Affects Billing?	Yes – inactive Projects lose certain features	No

Common Mistakes

Putting Everything in One Package

It can be tempting to place all graphics into a single package. However, Graphics Packages have a finite capacity, and performance may degrade as they grow larger.

Best Practice: Separate packages by graphic type, show segment, or workflow.

Confusing Project Status with Package Publishing

Setting a Project to Inactive is not the same as unpublishing a Graphics Package.

An Inactive Project displays a watermark on all outputs.
Publishing a Graphics Package makes the latest changes live.

Creating a New Project for Every Episode

Projects should represent long-term entities such as shows, productions, or clients—not individual episodes.

Best Practice: Reuse the same Project across episodes and update the content within the Graphics Packages as needed.

Still Unsure?

If you're setting up Flowics for the first time, start with one Project and one Graphics Package. You can always reorganize your structure later as your workflow grows.