Quick BB
PHP 8.2+ & MySQL Buy license · $79.95
Look & feel

How to Customize Your Forum Skin Colors

Build a custom forum color palette from your brand color, check WCAG contrast, and customize a skin safely by duplicating it first.

Updated 5 minute read The Quick BB team

Changing the colors of your forum skin is the fastest way to make a board feel like your own. A good custom palette matches your logo or subject, stays readable for every member and survives future updates. This guide explains how classic forum palettes are built, how to check contrast, and a safe workflow for customizing a skin.

How a classic forum palette is structured

Classic message boards use a small number of colors, each with a clear job. Once you understand the roles, changing a skin becomes a matter of swapping four or five values rather than redesigning every page.

Here is the default Classic Blue palette in Quick BB as a worked example:

RoleClassic Blue valueWhere it appears
Header#355A80Category header bars, table headings, navigation bar
Accent#819BB5Sub-headers, borders, secondary bars, highlights
Rows#DCE5EEForum and thread rows, postbit member column
Background#F5F7FAPage background behind the tables

The pattern is a dark header, a mid-tone accent of the same hue, a pale row tint and a near-white background. Text color, link color and border color complete the set. Every bundled skin follows a similar structure, which is why they look consistent; you can compare them in the skins table.

Check contrast before you commit

Dense forum layouts put a lot of small text on colored backgrounds, so contrast matters more than on a typical blog. The Web Content Accessibility Guidelines (WCAG) level AA ask for:

  • At least 4.5:1 contrast for normal text.
  • At least 3:1 for large text (roughly 24px regular or 18.7px bold and above).
  • At least 3:1 for the visual parts of interface components, such as input borders and focus outlines, against neighboring colors.

Level AAA raises normal text to 7:1. Applying the standard WCAG formula to the Classic Blue palette shows how roles affect text choice:

Text on backgroundContrast ratioResult
White on header #355A80about 7.2:1Passes AA, passes AAA
Header color #355A80 as link text on #F5F7FAabout 6.7:1Passes AA
Dark text #222222 on rows #DCE5EEabout 12.5:1Passes AA and AAA
Dark text #222222 on accent #819BB5about 5.5:1Passes AA
White on accent #819BB5about 2.9:1Fails for normal text

The lesson: mid-tone accent colors need dark text, while dark header colors need white text. When you change a color, recheck every text color that sits on it. Any free online contrast checker will calculate the ratio from two hex values.

Build your own palette in five steps

  1. Start from your brand color. Take the main color of your logo. If it is dark enough to carry white text at 4.5:1 or better, use it as the header color. If it is bright or light, darken it for the header and use the original as the accent.
  2. Derive the accent. Pick a lighter version of the header hue, roughly halfway to white. Plan for dark text on it.
  3. Derive the row tint. Go much lighter again, so dark text sits comfortably on it. Optionally create a second, slightly different row tint for alternating rows.
  4. Choose the background. A near-white with a hint of the same hue keeps tables standing out without glare.
  5. Set text and links. Use a near-black for body text and a color that passes 4.5:1 on both the row tint and the background for links. The header color often works.

Keep colors from fighting the status icons. Unread, sticky and locked indicators should still be easy to tell apart, and never rely on color alone to mean something.

Customizing a skin in the Style Manager

Quick BB includes an admin Style Manager, so you can change colors without editing PHP files. A safe workflow looks like this:

  1. Duplicate the skin you like. Never edit the bundled original directly. Duplicate Classic Blue (or another bundled skin) and rename the copy, for example "Our Club Blue".
  2. Use the color pickers. Adjust the header, accent, row and background colors with the color pickers, then the text and link colors.
  3. Fine-tune with CSS variables. For anything the pickers do not cover, adjust the skin's CSS variables. Because the colors live in variables, one change updates every place that role is used.
  4. Add your logo. Upload a skin logo so the header matches your new palette.
  5. Preview, then set as default. Check the index, a forum list, a long thread, the User CP and a posting form. When happy, make the new skin the default.

You can also enable or disable skins so the footer style chooser only offers ones you are proud of, and assign per-forum skins, for example a different color for a sponsor's subforum or an off-topic area.

Dark skins need their own checks

A dark skin is not just the light palette inverted. On a dark background, pure white text can feel harsh, so many designers use a light grey instead, while still keeping at least 4.5:1 contrast. Check link colors carefully: a link blue that works on white often becomes hard to read on near-black. The bundled Midnight Black is a full dark skin, which is a good starting point to duplicate rather than building a dark theme from a light one.

Also check images. Logos with transparent backgrounds and dark text can disappear on a dark skin, so upload a separate skin logo for it.

Share and back up your skin

Once your skin is finished, export it from the Style Manager and keep the file with your other backups. If you run several forums, import the same skin on each. Imported skins never execute PHP or JavaScript, so sharing skin files between sites does not open a security hole. Before upgrading the forum software, export your custom skins; see how to upgrade forum software safely and forum backup and restore.

Common mistakes to avoid

  • Choosing a bright brand color as the header and putting white text on it without checking contrast.
  • Making rows and background the same color, so tables lose their structure.
  • Using too many colors. Stick to one hue family plus neutral greys.
  • Forgetting focus outlines, which keyboard users rely on. They need 3:1 against surrounding colors.
  • Editing the bundled skin directly instead of a duplicate, which makes it hard to compare or roll back.

For the bigger picture of how skins, tables and the postbit fit together, read the classic forum design guide.

Frequently asked questions

What contrast ratio should forum text have?

WCAG level AA asks for at least 4.5:1 for normal text and 3:1 for large text. Interface parts such as input borders and focus outlines need at least 3:1.

Should I edit a bundled skin directly?

It is safer to duplicate the bundled skin and edit the copy. That way you can compare with the original and roll back easily.

Why does white text look bad on my accent color?

Mid-tone accent colors often do not have enough contrast with white. Use dark text on light and mid-tone colors and white text on dark header colors.

Get three guides like this every month, plus software update notices.Subscribe →