Skip to content
Hoody.com

The Hoody Displays service provides the HTML5 remote display client — a browser-based GUI that streams rendered desktop sessions to users over WebRTC. It handles the visual surface of the platform, from window rendering and input capture to screenshots, session sharing, and performance tuning. Use this service when you need to embed, customize, or programmatically control the remote display that your users see in their browser.

Below is an index of the sub-pages that document each area of the Display service.

Web Client Interface

Configure how the HTML5 display client is served, embedded, and connected. Covers the WebSocket entry point, the client page, and the initialization handshake.

Open Web Client Interface →

Input & Clipboard

Configure keyboard layouts, clipboard synchronization, and scrolling behavior between the local browser and the remote display.

Open Input & Clipboard →

Input Actions

Send low-level mouse, keyboard, and window-management events to automate the remote display — useful for scripting interactions and testing.

Open Input Actions →

Screenshots

Capture and retrieve display screenshots and thumbnails. Useful for previews, auditing, and AI-driven visual workflows.

Open Screenshots →

Session & Sharing

Configure session sharing, multi-user access, and read-only mode for collaborative viewing of a remote display.

Open Session & Sharing →

Health & Info

Health check endpoints and live API documentation surfaces for the Display service.

Open Health & Info →

Performance & Encoding

Tune video encoding, bandwidth limits, frame rate, and rendering quality to balance fidelity and resource use.

Open Performance & Encoding →

UI & Theming

Configure window decorations, toolbar visibility, and dark mode to integrate the display client with your application.

Open UI & Theming →

Feature Flags

Toggle optional features such as printing, file transfer, and video playback on or off per session.

Open Feature Flags →

Debugging

Enable debug flags and verbose logging to troubleshoot connection, rendering, or input issues.

Open Debugging →