Free Screenly Player with every Business or Enterprise yearly plan. How it works →

August 17, 2026

Landscape, Portrait, Full HD, UHD and Anywhere are no longer automatic labels

Screenly used to put 5 labels on screens by itself: Landscape, Portrait, Full HD, UHD and Anywhere. Screenly maintained them from each screen’s own properties, which meant you could not rename them, delete them, or decide which screens carried them.

They were not describing screens well enough to earn that. All but one of them stood in for properties a screen already reports, and the two resolution labels were thresholds rather than descriptions: Full HD went on anything from 1920x1080 up to just below 4K, so a 1440p display and a 1080p one carried the same label, and a display below 1080p got neither. Displays that aren’t 16:9 fared worse, because both edges had to clear the bar: a 3840x1600 ultrawide counted as Full HD rather than UHD, and a 1680x1050 display got no resolution label at all.

The groupings were also seldom a useful target. Every portrait screen, or every Anywhere screen, spans different sites, rooms and purposes that have nothing else in common.

So they are ordinary labels now. The ones in your workspace keep the screens they were on, and you can rename, delete or apply them like any label you made yourself.

If a playlist plays on one of these labels: it now plays on the screens that carried the label at this release, and that set no longer updates by itself. A new landscape screen will not join the Landscape label on its own, and a screen you rotate will not change labels. Check any playlist that targets these five, and either maintain the label yourself or assign the screens directly.

If your workspace already had its own label with one of those five names, the two are now a single label holding both sets of screens.

Targeting content by a screen’s own properties, rather than through a label standing in for them, is what we are working on instead.

For developers

The label type field on API v4 and v4.1 changes with this, and filtering by a removed type now returns an error. The API side of this change lists the values that remain and what to update.