Where Is the Hyper Terminal Config File?
Hyper reads its .hyper.js config from the OS app-data folder, with the old home-directory file as fallback.
Last updated
Hyper's config is a JavaScript file called .hyper.js. Current builds read it from the OS app-data dir: ~/Library/Application Support/Hyper on macOS, %APPDATA%\Hyper on Windows, ~/.config/Hyper on Linux. Fonts, colors, shell, and the plugin list all live in that one file.
The legacy location was ~/.hyper.js in your home folder, and it still works as a fallback. The catch: when both exist, the app-data copy wins silently. Old guides predate the move, which is why edits mysteriously stop applying after updates.
Where Hyper stores this, by platform
~/Library/Application Support/Hyper/.hyper.js
Official location per hyper.is docs. Legacy ~/.hyper.js still applies only when this file is absent. Plugins may override values set here.
%APPDATA%\Hyper\.hyper.js
Same precedence rules as macOS. An empty .hyper.js here famously breaks launches; deleting the Hyper folder fixes it.
~/.config/Hyper/.hyper.js
Respects $XDG_CONFIG_HOME. Same fallback to ~/.hyper.js when absent.
Frequently asked questions
I edited .hyper.js and nothing changed. Why?
You are editing the wrong copy. Newer builds read the app-data location and ignore ~/.hyper.js when both exist. Move your edits to the app-data file, or delete it so the home file applies again.
How do I open the right config file directly?
Open Hyper and press the shortcut for Preferences (Cmd+, on Mac), which opens the active file in your editor. That guarantees you edit the copy Hyper actually loads.
Notice an outdated path? Let us know.