Design Guide

Create distinctive, professional faceplates that stand out from generic plugin UIs. This guide covers layout patterns, color theory, control naming, and common mistakes to avoid.

Design Principles

1. Personality Over Function

Your plugin’s appearance should reflect its sonic character, not just its technical function. A warm vintage compressor shouldn’t look like a clinical utility.

2. Less is More

Fewer controls = more impact. Every element should earn its place. Ask: “Does this need to be here?“

3. Visual Hierarchy

Size and position communicate importance:

  • Largest = most important
  • Center = primary focus
  • Edges = secondary controls

4. Consistency

Pick a style and stick with it:

  • Same knob style throughout
  • Consistent label formatting
  • Unified color palette

Guides

Layout Patterns

Five archetypes for creating aesthetic, personality-driven layouts:

  • Hero Element
  • Asymmetric
  • Minimal
  • Immersive
  • Clustered

Choosing Visualizers

How to select the right visualizer based on plugin personality, not just function.

Control Naming

Give your controls evocative names that make users want to turn the knob.

Color Theory

Color principles for controls and visualizers.

Anti-Patterns

Common mistakes that make plugins look generic. Avoid these.

Quick Reference

Widget Sizes (Grid Units)

WidgetSmallMediumLarge
Knob2×23×34×4
Slider (V)1.5×62×8-
Toggle1.5×1.52×12×2
Visualizer4×36×49×5

Padding Constants

AreaGrid Units
Faceplate edge1
Section inner1
Section label height1.5
Widget gap0.5
Widget to section edge1

Aspect Ratios

Control CountTypical SizeAspect
3-4 minimal260-340 × 300-380Square-ish
5-7 standard340-480 × 320-420Varies
8-10 complex420-560 × 380-480Wider
Immersive400-520 × 280-360Wide

Design Process

  1. Start with function - What does the plugin do?
  2. Define personality - Warm? Aggressive? Clean? Vintage?
  3. Choose layout pattern - Hero, minimal, asymmetric, etc.
  4. Select widgets - Knobs, sliders, visualizer
  5. Apply colors - Match personality
  6. Name controls - Evocative, not technical
  7. Review - Does it feel right?

Checklist

Before finalizing your design:

  • Does the design match the plugin’s sonic character?
  • Is there clear visual hierarchy?
  • Are controls sized appropriately?
  • Is spacing consistent?
  • Do control names evoke feeling?
  • Does the visualizer serve a purpose?
  • Would you recognize this plugin from its silhouette?

5 items under this folder.