Oraphim reference

Reference pages answer what a control or capability is. For full start-to-finish projects, use Step-by-step projects; for first-time setup, use Getting started.

Core references

• Keyboard shortcuts — confirmed default shortcuts. The current build does not expose a user-facing shortcut remapping editor.
• Effects — artist-facing catalog generated from Oraphim's canonical effect registry.
• Nodes — graph concepts, connection discipline, validation and persistence.
• Panels — selection/context behavior and workspace panels.
• Blend modes — compositing behavior and practical use.
• Project settings and Preferences.
• File types and Supported formats.
• Export formats plus Professional master workflow.
• MCP tools plus MCP permissions & security.
• Troubleshooting reference.

Reference rule

The manual documents shipped/verified behavior. A roadmap item, hidden development command, compatibility name, or test-only capability is not presented as an artist feature simply because it exists somewhere in source.

How to use reference pages

Reference pages answer “what does this control, format, panel, node, effect, or shortcut mean?” They are intentionally different from tutorials, which answer “how do I finish a task?” Use the reference while working when you need exact names, supported formats, shortcut behavior, MCP surface information, or the effect catalog; use the step-by-step projects when you need an end-to-end learning path.

For release-sensitive facts such as export codecs, AI model behavior, or effect counts, prefer these current reference pages over old screenshots, third-party posts, or remembered UI labels.