Everything in one place.
Feeds, channels and Mini Apps without the extra steps.
Choose a platform. We’ll show verified downloads as they become available.
Select your device below
YOUR DEVICE / 01
Desktop application
A focused desktop experience designed for Windows.
Choose your processor if it cannot be detected.
The official download will appear here after release.
Select a compatible installer below.
Only verified public releases appear here. Internal builds aren’t offered as downloads.
06 / BROWSER EDITION
The same client experience, built for your browser. No installation.
Checking basic WebAssembly support
Three things that shape every part of GenyCaster.
Feeds, channels and Mini Apps without the extra steps.
Local-first views that make returning feel familiar.
HyperSnap by default. Switch to Snapchain when you choose.
03 / TAKE A CLOSER LOOK
Just two things to explore, when you want the details.
Shared Qt / QML foundations. A local-first experience. Your choice of protocol.
Explore the projectFIG. 03 RENDERING PATHS
Qt Quick builds the scene. The active graphics backend and driver determine whether rendering runs on the GPU or CPU.
Acceleration runs through a platform API and driver.
When acceleration is active, the GPU draws graphics. The CPU still handles layout, app logic and submitting commands.
A virtual adapter may reach the host GPU.
A guest driver and hypervisor determine whether graphics are GPU-backed, CPU-rendered or unavailable.
When rasterization moves onto the CPU.
This llvmpipe example draws with CPU resources. Other software backends use different rendering paths.
GenyCaster’s Rendering Quality → Efficiency profile lowers some rendering and effect costs. Power Save reduces animated media and background motion; Reduce Motion removes selected repeated and spatial animations. These settings do not switch the app to a GPU or guarantee smooth frames.
Mesa llvmpipe performs OpenGL rendering on the CPU while keeping Qt RHI active. Qt Quick’s separate Software adaptation uses a raster paint engine and does not support every shader-based effect. On Windows, Direct3D may use WARP software rasterization. For Linux guests identified as Parallels, GenyCaster requests OpenGL only when no Qt backend override is set, and requests Mesa software rasterization only if that environment flag is also unset. This is not a universal VM fallback or a guaranteed driver outcome.
Windows usually defaults to Direct3D 11; macOS and iOS use Metal; Linux typically uses OpenGL; Android often uses OpenGL ES; and WebAssembly uses browser-backed WebGL. Alternatives such as Vulkan depend on the installed Qt build and driver. Even a physical device with a GPU may run software rendering.
No directly comparable end-to-end FPS, GPU timing, CPU load or power measurements have been published for these environments. The diagram does not detect your active GPU or graphics API. Actual behavior depends on the backend, driver, resolution, effects and workload. Qt documentation
04 / BUILDING IN THE OPEN
Follow GenyCaster on GitHub. The source repository is currently private; public access is not yet enabled.