GENYCASTER / THE SOCIAL CLIENT
GENYCASTER / 2026

Farcaster.
Your way.

A simpler way to follow, connect and explore Farcaster.Your feed. Your conversations. Your choice of protocol.

YOUR SPACE  /  YOUR DEVICE  /  YOUR WAY LOCAL-FIRST BY DESIGN
01  /  FIND YOUR VERSION

Made for your device.

Choose a platform. We’ll show verified downloads as they become available.

Select your device below

YOUR DEVICE / 01

Windows

Desktop application

A focused desktop experience designed for Windows.

ArchitectureChecking your device

Choose your processor if it cannot be detected.

RELEASE STATUS

Coming soon.

The official download will appear here after release.

In preparation

Only verified public releases appear here. Internal builds aren’t offered as downloads.

06 / BROWSER EDITION

The browser edition.

The same client experience, built for your browser. No installation.

Checking basic WebAssembly support

WEBASSEMBLY / QTAccess link not enabled yet
02  /  THE IDEA BUILT FOR HOW YOU CONNECT

Less noise. More connection.

Three things that shape every part of GenyCaster.

01 / YOUR SPACE

Everything in one place.

Feeds, channels and Mini Apps without the extra steps.

02 / YOUR PACE

Built around what you do.

Local-first views that make returning feel familiar.

03 / YOUR ROUTE

Choice is part of the design.

HyperSnap by default. Switch to Snapchain when you choose.

03  /  TAKE A CLOSER LOOK

Curious? Go a little deeper.

Just two things to explore, when you want the details.

01 / STRUCTURE How does GenyCaster connect everything?One client · Desktop, mobile and browser · Two protocol routes
03  /  UNDER THE HOOD ONE CLIENT · MULTIPLE ROUTES

One client.
More than one path.

Shared Qt / QML foundations. A local-first experience. Your choice of protocol.

Explore the project
One interface across native and web targets. The active protocol is user-selectable.
02 / RENDERING How does GenyCaster use your CPU & GPU?How graphics work moves between CPU and GPU

FIG. 03 RENDERING PATHS

From silicon to screen.

Qt Quick builds the scene. The active graphics backend and driver determine whether rendering runs on the GPU or CPU.

QT QUICK / SCENE GRAPH
BACKEND-DEPENDENT RENDERING
01 / NATIVE GPU path · if active

Real device

Acceleration runs through a platform API and driver.

APPLICATIONGenyCasterQt Quick / Scene Graph
GRAPHICS BACKENDAPI + driverMetal · D3D · GL · Vulkan
DEVICE CHIPSET
CPUUI + commands
GPUFrames
DISPLAY

When acceleration is active, the GPU draws graphics. The CPU still handles layout, app logic and submitting commands.

POSSIBLE TENDENCIES / not measured
Effects supportBackend*
Motion potentialOften higher
CPU raster loadOften lower
02 / VIRTUALIZED Host + driver dependent

Virtual machine

A virtual adapter may reach the host GPU.

GUEST APPLICATIONGenyCasterQt Quick / Scene Graph
VIRTUAL GRAPHICSVirtual adapterGuest driver / hypervisor
HOST HARDWARE
CPUHost / guest
GPUIf exposed
DISPLAY

A guest driver and hypervisor determine whether graphics are GPU-backed, CPU-rendered or unavailable.

POSSIBLE TENDENCIES / not measured
Effects supportVaries
Motion potentialVaries
CPU raster loadVaries
03 / FALLBACK CPU-rendered example

CPU rendering

When rasterization moves onto the CPU.

APPLICATIONGenyCasterQt Quick / Scene Graph
EXAMPLE · LINUX / MESAOpenGL / llvmpipeRHI with CPU rasterization
CPU RASTERIZATION
CPUDraws frames
GPUNot used here
DISPLAY

This llvmpipe example draws with CPU resources. Other software backends use different rendering paths.

POSSIBLE TENDENCIES / not measured
Effects supportBackend*
Motion potentialOften lower
CPU raster loadOften higher
These are illustrative tendencies, not benchmark scores or real-time diagnostics. Segments do not represent measured FPS or percentages. More CPU raster load means more processor work. *Effects support depends on the chosen graphics backend. Results depend on the driver, hardware and workload.
Active renderer Depends on VM Not used for rasterization
Running without dependable GPU acceleration?

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.

Technical notesWhat changes with software rendering and each platform?

Software rendering is not a single backend.

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.

Typical platform graphics APIs

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

See where it’s going.

Follow GenyCaster on GitHub. The source repository is currently private; public access is not yet enabled.

Explore GitHub