Where Does Hyperion Store Config?
Hyperion keeps LED layouts, effects and instance settings in a config tree on Linux. Path and backup routine.
Last updated
Hyperion centers on a config tree with per instance settings, LED layouts and effect files. The web interface reads and writes that tree. Captures never persist since the grabber streams live.
That single tree design makes moves one copy with the service stopped. Effect collections ride along with layouts. New strips need count and order fixes after restore, which the web UI handles.
Where Hyperion stores this, by platform
~/.config/hyperion
Instance configs, LED layouts and custom effects. Exact filenames may vary by Hyperion version, so confirm against the web UI file browser. Stop the service before copying.
Frequently asked questions
How do I back up Hyperion?
Copy the hyperion config tree with Hyperion quit, especially instance configs and custom effects. Layouts, grabber choices and smoothing travel together. Recalibrate LED counts on new hardware even after a faithful copy.
Where are my LED layouts?
In instance config files inside the config tree, one per LED layout. The web UI edits the same files, so hand edits and UI edits share one source of truth. Keep a versioned copy before rewiring strips.
Notice an outdated path? Let us know.