--- title: Browser-Based Digital Signage Software description: Plan browser-based signage with the Loopvew Web Player. Turn any device with a modern browser into a screen — no installation, fast pilots. type: platform os: web platformName: Web Player platformLogo: /svgs/brands/web.svg deviceType: Devices with a compatible web browser status: planned compatibility: - label: Device family value: Browser-equipped devices; compatibility to confirm - label: Player type value: Browser-based playback - label: Requirements value: Browser versions, storage, and device policies to confirm - label: Availability value: Planned; public player URL coming soon devices: - name: Existing PCs and laptops note: Open the player URL and the screen is live — the fastest way to pilot signage on hardware you already have. icon: laptop - name: Smart TV browsers note: Built-in TV browsers can work for simple content — confirm the engine and media support first. icon: tv - name: Tablets note: Counter and meeting-room screens driven by a browser session. icon: tablet - name: Chromeboxes and mini PCs note: Browser-centric hardware that needs no native player install. icon: monitor highlights: - title: No installation text: Open the player URL, pair the screen, and publish — nothing to deploy per device. icon: zap - title: Any modern browser text: Chrome, Edge, and other Chromium-class browsers — the final supported list ships with the release. icon: globe - title: The fastest pilot path text: Evaluate Loopvew on a laptop or spare PC today, then move to a native player when you scale. icon: play - title: The same CMS content text: Playlists, schedules, multi-zone layouts, and widgets — the same content workflow as every platform. icon: cloud - title: Kiosk via OS tooling text: Fullscreen and lockdown come from the device's kiosk mode or browser policy, not the player itself. icon: lock - title: Offline playback text: Planned — keep downloaded content playing through outages; confirm browser storage policy first. icon: cloud-off steps: - name: Confirm availability text: The Web Player is planned and has no public URL yet. Contact Loopvew to register your interest and confirm the supported browsers. - name: Open the player and pair text: When released — open the player URL on the screen's device and enter the on-screen pairing code in the CMS. - name: Publish and evaluate text: Publish a test playlist, then verify fullscreen behavior, autoplay, and session persistence before relying on it. management: - title: Content updates from the CMS text: Publish new playlists and schedules; the browser player picks them up like any other platform. icon: refresh-cw - title: Remote screenshots text: Planned — capture what is playing where the browser environment allows it. icon: camera - title: Restart via device tooling text: Browser players rely on the OS, kiosk policy, or MDM for reboot and power control. icon: power - title: Kiosk via browser policy text: Fullscreen, auto-launch, and lockdown come from the browser's kiosk mode or device management. icon: lock widgets: - Weather - News and RSS feeds - YouTube videos - Live streams - Calendars and schedules - Web dashboards - Social media feeds - Clock and date comparison: title: Web Player vs a native player app intro: The Web Player is the fastest way to a first screen. Native players go further for permanent installations. columns: - Consideration - Web Player - Native player app rows: - - Installation - None, open a URL - Install per device - - Device controls - Browser-limited - Reboot, screenshots, power - - Offline playback - To be confirmed - Keeps playing - - Best for - Pilots and events - Permanent installs useCases: - label: Conference rooms href: /solutions/use-cases/conference-rooms icon: users - label: Internal comms href: /solutions/use-cases/internal-comms icon: megaphone - label: KPI dashboards href: /solutions/use-cases/dashboards icon: layout-dashboard - label: Wayfinding href: /solutions/use-cases/wayfinding icon: map-pin supportedFeatures: - Evaluate playback without a desktop player installation - Plan a browser session linked to your CMS workspace - Review content and authentication requirements before deployment knownLimitations: - The Web Player is not publicly released - A browser player is different from the browser-based CMS - Device restart, power, and kiosk controls may require external management - Offline playback, supported browsers, and storage limits are unconfirmed faq: - question: Can I use a web browser for digital signage? answer: Yes — a browser player is the fastest way to put signage on a device you already own, with nothing to install. For permanent unattended screens, a native player gives deeper device control and guaranteed offline playback. The Loopvew Web Player is planned; contact the team for availability. - question: Is the Loopvew Web Player available now? answer: The Web Player is planned and has no public player URL yet. Contact Loopvew for availability. The CMS login page is not a substitute for a screen-player URL. - question: Is the Web Player the same as the Loopvew dashboard? answer: No. The dashboard is where you manage content and screens. A Web Player would be a separate browser session that displays assigned content on a screen. - question: Which browsers will be supported? answer: The supported browser and version list is not finalized. Device operating system, graphics support, storage policies, and autoplay restrictions also need validation. - question: Can a browser player reboot a device or control display power? answer: A normal browser session does not provide general operating-system administration. Such controls may require a native player, managed kiosk environment, or external device-management tool. - question: Will the Web Player run offline? answer: No offline guarantee is currently published. Browser storage can be restricted or cleared, and live content needs a connection. Test the final player and policies before relying on disconnected operation. - question: Can I use a smart TV's built-in browser? answer: Do not assume that a TV browser matches a current desktop browser. Confirm its engine, media capabilities, storage, fullscreen behavior, and supported player status before choosing it for signage. --- ## Why consider a browser player? A browser-based player could let you evaluate signage on an existing computer without first deploying a desktop application. That can reduce installation work for a pilot, but it does not remove the need to configure the device for unattended use. Loopvew's Web Player is planned. It is distinct from the cloud CMS: the CMS prepares content, while a player displays assigned content on a screen. Signing into the dashboard does not turn that browser into a signage player. ## Plan browser-based playback The three steps below summarize the planned flow — confirm availability, open the player and pair, then publish and evaluate. What follows covers the browser boundaries that shape a browser-based deployment. Do not build a kiosk around a guessed URL or the CMS login page. Wait for the actual player endpoint and its deployment instructions. ## Understand browser boundaries Web content is affected by permissions and security policies. A browser may block audio autoplay, clear local storage, suspend background work, or require interaction to enter fullscreen. Authentication for third-party dashboards can also expire independently of the signage session. Power control, operating-system restart, and silent application updates are not ordinary browser capabilities. If those are required, compare a native player and an appropriately managed operating system. ## When a native player is a better fit For installations that must recover without someone touching the screen, evaluate the full device-management path rather than only the first successful playback. Native and browser players may have different feature boundaries. Explore the available [Windows](/platforms/windows), [Linux](/platforms/linux), and [Android](/platforms/android) players. Use the Web Player when its confirmed capabilities match your workload, not simply because the device has a browser icon.