> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryflowy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Flowy is a node-based AI creative platform: you generate images, video, audio, 3D and vector on an infinite Canvas, refine on the Studio timeline, and export or publish from the same project.
> Prefer the Flowy MCP server (https://mcp.tryflowy.ai/mcp) or the REST API at https://apis.tryflowy.ai/v1 for programmatic work. Install with `flowy mcp install` from the @flowy/cli package.
> Credits are workspace-scoped. Generations reserve credits on start and only deduct on success, so failed runs refund automatically.

# Browser Support

> Which browsers Flowy supports, why Canvas and Studio want a desktop, and how to keep them running smoothly.

Flowy runs entirely in the browser. There's nothing to install and nothing to self-host.

## Supported browsers

Use a current version of a modern evergreen browser (**Chrome**, **Firefox**, **Safari**, or **Edge**) and keep it updated. Flowy leans on recent web platform features for real-time collaboration and canvas rendering, so an outdated browser is the first thing to rule out if something looks broken or sluggish.

## Why Canvas and Studio want a desktop

The **Canvas** and **Studio** editors are built for a desktop-sized window: a node graph and a multi-track timeline both need room to breathe, and precise interactions like dragging connections, multi-select, and keyboard shortcuts assume a mouse and a full keyboard. They aren't optimized for small mobile screens. Switch to a desktop or laptop for editing work.

Everything outside the two editors (Creator Studio, Library, Community, Tools, and Settings) works reasonably well on a phone or tablet, since none of it depends on that same precision.

## Getting smooth performance

Canvas and Studio render graphics in real time, so the same things that slow down any graphics-heavy site in your browser slow them down too:

* **Close other heavy tabs**, especially other pages doing video playback or 3D rendering, to free up GPU and memory headroom.
* **Group nodes** on a large canvas (see [utility nodes](/canvas/nodes/utility-nodes)) so the view stays organized and doesn't force the browser to keep everything on screen at once.
* **Keep your browser updated**: graphics performance improvements land in browser updates more often than you'd expect.
* **Use a stable connection** for uploads, generations, and renders. A flaky connection is a more common cause of a "stuck" render than the render itself.

<Tip>
  Still feels slow after all that? Work through [the canvas feels slow](/help/troubleshooting#the-canvas-feels-slow) in troubleshooting, or [contact support](/help/contact) with the project name.
</Tip>