# Docs

- Guide
  - [What is FrameOS?](/guide): An operating system for single-function smart frames. Runs on a Raspberry Pi or an ESP32, renders on e-ink, HDMI and LCD displays. Standalone, self-hosted, or managed from FrameOS Cloud - everything renders on the device.
  - [A standalone frame](/guide/standalone): Run a single frame with nothing else - flash a generic FrameOS image to a Raspberry Pi, set it up from your phone, and manage it from the frame's own admin page.
  - [The backend](/guide/backend): Install the self-hosted FrameOS backend with one command, via Docker, or as a Home Assistant add-on.
  - [FrameOS Cloud](/guide/cloud): Manage frames from cloud.frameos.net without running a backend - enroll a Pi or ESP32 in minutes, assign scenes from the store, see logs and previews. Free while in beta.
  - [The Raspberry Pi](/guide/raspberry): Choose a Raspberry Pi, then flash either a prebuilt FrameOS SD image or stock Raspberry Pi OS Lite.
  - [The ESP32](/guide/esp32): Run FrameOS on an ESP32-S3 microcontroller - flash from the browser, render full scenes on-device, sleep on a battery, update over the air.
  - [Pico W & Inky Frame](/guide/pico): Run FrameOS on a Raspberry Pi Pico W or Pico 2 W - including the Pimoroni Inky Frame - as a thin client that renders on the backend.
  - [Virtual frames](/guide/virtual): Run a frame with no hardware at all - the backend renders the scene and serves it as an image URL and a self-refreshing kiosk page.
  - [First deploy](/guide/first-deploy): Add a frame to the backend, install a few scenes, and deploy them to the device.
  - [Editing scenes](/guide/scenes): Build scenes visually with the node-based editor - events, apps, data sources and state.
  - [The scene store](/guide/scene-store): Browse, preview, fork and install community scenes from scenes.frameos.net - on cloud-managed frames with one click, or on a self-hosted backend by pasting a link.
  - [Editing apps](/guide/apps): Every node on a scene is an app you can fork and edit - in JavaScript, or in Nim.
  - [Big images on small devices](/guide/images): How FrameOS renders a 12-megapixel photo on a device with 8 MB of RAM - streaming decoders, bounded decodes, spooling and caching.
  - [Controlling the frame](/guide/control): Every frame serves its own web app and HTTP API on port 8787. Whether it's standalone, self-hosted or cloud-managed - control it from anything that speaks HTTP.
  - [Useful settings](/guide/settings): Access keys, QR codes, asset storage, power management, nightly reboots and debug logging.
  - [FrameOS Remote](/guide/remote): The optional on-device companion that connects frames back to the backend for logs, metrics, terminal access and remote management.
- Devices
  - [Device database](/devices): Every display FrameOS can drive - 120+ e-ink, LCD and HDMI displays with specs, colors, resolution and setup notes.
  - [Waveshare buying guide](/devices/waveshare-other-displays): Which Waveshare e-Paper panels are tested, and what to know before buying.
- 3D-printed cases
  - [3D-printed cases](/cases): Design a parametric case for your panel and Pi in the browser, download an STL, print it.
- [FAQ](/faq): Frequently asked questions about FrameOS.