Put your first screen to the test

How do I connect and publish to a screen?

1. Prepare a representative display. Check resolution, portrait or landscape orientation, viewing distance, power and network access. Use the same kind of player you plan to roll out.
2. Create your account and obtain the suitable player. Confirm the installation instructions and supported version for your hardware. Keep the account and player pairing code private.
3. Pair the player. Use its pairing code in your dashboard, name the screen for its location, and check that it reports online before assigning content.
4. Create a small test playlist. Include an actual image, video and any required live app. Review generated prices, spelling and imagery before publishing an AI design.
5. Publish and inspect the physical display. Confirm the right screen receives the right content. Check readable text, cropping, video playback and any audio requirements at the viewing position.
6. Test a scheduled change. Verify the intended timezone and repeat pattern, then observe the transition between two real playlists. Record the result before adding more screens.

Explore scheduling and monitoring features, content apps and integrations, or AI signage design.

What happens when the connection drops?

Cached media and live content are different. A player may continue with downloaded media, while a webpage, stream, queue or current-data app can still need its source connection. Offline behaviour also depends on the player, available storage and licence terms. Test it with your actual content rather than assuming every app stays current.

• Allow the test content to download, then disconnect the network briefly in a controlled trial.
• Check which media keeps playing, which feeds stop updating and whether the viewer can tell that data is old.
• Reconnect and confirm both player status and the latest published content recover.
• Test a restart separately; a running player's cache is not proof that a device can start offline.
• Do not rely on signage as your sole emergency or safety communication channel.

A remote screenshot shows a moment in time; it does not prove display power or continuous audience exposure. Use the screen-fleet monitoring guide to plan operational checks.

What should I confirm before adding locations?

Record the tested device, player version, content formats, timezone, network recovery and person responsible for support. Agree which people can publish to each screen group. Confirm software billing, introductory duration, taxes, storage and AI usage separately from hardware and installation.

Compare current DigiSign plans, build a digital signage budget, and choose the appropriate industry workflow. If the trial exposes a device or content limitation, resolve it before duplicating that setup.