Digital signage content falls into two categories: static (images, videos, slides) and dynamic (data-driven widgets, live feeds, interactive elements). Static content is easy to create but impossible to scale. Dynamic content requires initial setup but runs autonomously after that — updating thousands of screens from data sources without daily human effort. The ROI of digital signage depends entirely on which type you choose.
When Content Type Matters
- Lobby welcome screens — dynamic: pull today's meetings from Exchange, show visitor names from the access control system
- Retail promotions — hybrid: branded video loop in one zone, live pricing from POS in another
- Corporate KPIs — dynamic: pull from BI tools, ERP, or databases. Update every 5 minutes without human action
- Wayfinding — dynamic: room availability from booking system, real-time queue information
Types of Content
Data-Driven Widgets (Highest Value)
Templates connected to live data sources: CSV, JSON, XML, REST APIs, calendar feeds, databases, IoT sensors. SpinetiX has 250+ widget-constructors for these connections. The template renders data in real time on the player. No manual updates. No human in the loop. This is the content type that justifies the investment in digital signage infrastructure.
Video & Animation
H.264 (MP4) up to 4K resolution. H.265/HEVC on iBX440 flagship. SpinetiX renders video with hardware acceleration — no dropped frames over extended runtime. Multi-zone capability: video in one zone, data widgets in others, all from a single player. Ideal for brand content, product demos, and ambient loops.
Images & Graphics
JPEG, PNG, SVG. SVG is recommended for graphics because it scales to any resolution without quality loss. SpinetiX renders SVG natively — the entire jSignage content framework is SVG-based. Use high-resolution images for photography, SVG for charts, diagrams, and branded elements.
Multi-Zone Layouts
Divide one screen into multiple zones running independent content: header bar with logo and time, main zone with video, ticker bar with news feed, sidebar with weather and prayer times. Each zone updates independently. One player handles all zones — no external multiplexer needed.
IPTV & Live Streams
SpinetiX players can display IPTV streams (multicast/unicast) alongside other content. A hospital waiting room can show live TV in one zone, queue numbers in another, and health tips in a third. All rendered by one iBX440 drawing 6W of power.
Interactive Content
Touch-screen interactivity for wayfinding, self-service kiosks, and product catalogs. SpinetiX supports HID touch input natively. Users navigate through menus, maps, or product information. The player handles all interaction logic locally — no cloud round-trip for button presses.
Key Parameters
| Content Type | Format | Best For |
|---|---|---|
| Data widgets | JSON, XML, CSV, REST API, ICS | KPIs, schedules, live feeds — highest ROI |
| Video | H.264 MP4, H.265 (iBX440) | Brand content, product demos, ambient |
| Images | JPEG, PNG, SVG | Photography, graphics, diagrams |
| IPTV | Multicast/unicast streams | Live TV, events, surveillance overlay |
| Interactive | HID touch input | Wayfinding, kiosks, catalogs |
| Multi-zone | Layout + independent zone content | All of the above, simultaneously |
Common Mistakes with Content Types
- Using video where data widgets would work. A video of today's menu requires daily rendering and upload. A data widget pulling the menu from a spreadsheet updates automatically forever. Choose the right content type for the job.
- Exporting everything as video. PowerPoint → video = static content that can't respond to data changes. Design native templates with data bindings. The initial setup time pays off within the first week.
- Ignoring multi-zone layouts. Running a single full-screen video is simple but wastes the player's capability. A multi-zone layout with video + data + ticker delivers 3x more value from the same hardware.
- Not planning for content lifecycle. Who updates the content? How often? If the answer involves a human every day, you're doing it wrong. See content automation →