Knowledge
Concepts
A handful of ideas explain how Screenly works: the screens you manage, the content they show, the timing behind it, and the structure that organizes who can do what. Understand these, and you understand Screenly.
The concepts build on each other, so read them in order, or jump straight to what you need.
Start here
1Screenly
See how the whole system fits together. The fastest way to make sense of everything else.
Get startedScreens & deployment
What a screen is, and the two ways to run Screenly on it.
Content & delivery
What you show, when it shows, and how it reaches the screen.
Content
The raw material of your signage, from images and video to web pages and apps.
Apps
Live, data-driven content on your screens, and where it fits.
Playlists
What decides what each screen actually shows.
Scheduling
The right thing on screen at the right time, planned in advance instead of switched by hand.
Content delivery
The path your content takes to each screen, and how caching keeps it playing offline.
Organization & access
The structure behind your teams, access, subscription, and outside connections.
Build with Screenly
Screenly is built to be built on, not only used. Automate it with the API and CLI, bring in AI through the MCP server, drive content with predicates, build your own apps, and even put your own product in front of it.
Screenly as a platform
What it means that Screenly is headless, and the range of what you can build on it.
Building apps
Build your own apps and run them on Screenly, with code on the device and secrets that never leak.
Web pages on screens
Make a web page built for people work as signage: shape it, reach it when it is private, and let it adapt per screen.
CLI
The command-line way to run Screenly, built for scripting and automation.
Predicates
The engine behind scheduling, and how to drive content from live data.
MCP server
A bridge that lets AI assistants understand and work with Screenly.