A XenForo board does not need a paid skin to look like a product. It needs a child of Default, a logo, a palette, and someone who will not fork PAGE_CONTAINER. A paid framework (UI.X 2, XenBase) is a different purchase: you are buying a system of templates and an upgrade cadence. A commissioned custom style is a third purchase: you are buying hours, a maintenance contract you must write down, and a merge queue that is yours alone.
This is a total cost comparison of those three paths on XenForo 2.3. It is not a “best themes of 2026” ranking, not the pre-flight checklist, and not the breakage cookbook. Read those before you import anything. It is also not the 2.3 variation switch — if “custom” means “we want dark mode,” you already have it.
Prices below are Resource Manager list figures recorded for this series (Styles 2.x, mid-2026). They change. Re-check the live resource before you invoice anyone. Designer day-rates are estimates, labelled as such — this article will not pretend a public page published a standard freelance rate.
The three honest products
Say the sentence before you open the Resource Manager.
| Path | What you actually buy | What you still own |
|---|---|---|
| Stock child-of-Default | Your time. $0 extra to XenForo for the style | Palette, logo, extra.less, TMS. Every core upgrade. |
| Premium parent (framework or one-shot) | A ZIP + updates for as long as the author ships them | Child customizations, add-on tax, merge after their updates |
| Commissioned custom | Hours, a unique parent (or a heavily forked child) | Every future XF point release, unless you also bought retainers |
Official: a Style is HTML templates + CSS/LESS + style properties. Pre-built styles live in the Resource Manager category Styles 2.x. Applying one is supposed to take a few minutes. The minutes are the import. The cost is the years after.
There is a fourth path people pretend is free: edit Default in place. That is not a path. That is how you turn every 2.3.x into a yellow outdated-template list. Create a child. The checklist already said so.
What “TCO” means for a style
Write one column per path. Zero is allowed only if the line is truly zero.
| Line | What belongs on it |
|---|---|
| Licence / ZIP | RM price, or $0 for child-of-Default |
| Required add-on | UI.X 2 needs the UI.X add-on. A one-shot may not. Custom may need nothing — or a private add-on |
| First-week labour | Import, child, variations, email style, three-session test |
| Merge labour per year | Core XF updates + vendor updates + your extra.less |
| Add-on tax | Portal, widgets, listing CSS, stream pages that assume the old parent |
| Host tax | Framework rebuilds that hit file limits (cookbook) |
| Exit cost | Hours to re-parent onto Default if the vendor goes quiet |
| Risk | Unmaintained parent (Shades of Grey last update 2022; Uniform last update Sep 2024) |
Do not compare month-one stickers. A $30 skin you cannot merge is more expensive than Default plus a Saturday of palette work. A $59.50 gaming skin that already has 2.3 variations can be cheaper than commissioning a dark mode someone will paint with hex.
Staff time is still the largest line, the same way it is in the platform cost comparison. If nobody on the team will open Appearance → Outdated templates, do not buy a unique parent.
Path A — child of Default
This is the default professional shape.
- Appearance → Styles → Add style, parent = Default style.
- Logo and Header/logo row via style properties.
- Color palette + Basic colors (
@xf-paletteNeutral3,@xf-textColor). - Enable variations if you want light/dark. Style type Light / Dark on the two halves.
extra.lesson the child for what properties cannot do.- Template modifications, not direct edits, for the one markup change you cannot avoid.
- HTML email stays on stock Default (light) unless you measured a reason not to.
Official property types cover more than people think: colours, text, numbers with units, switches, multiple-choice, CSS groups (text / background / border / padding / extra CSS). A surprising number of “we need a designer” tickets are a Header/logo row and a palette.
What this path wins.
- $0 incremental licence.
- Core upgrades apply. You merge your child, not a vendor’s opinion of
PAGE_CONTAINER. - 2.3 variations are first-class. You do not buy night mode.
- Exit cost is near zero. You already are on Default’s tree.
- Any contractor who has read the styles manual can pick it up.
What this path loses.
- You will not look like a magazine demo on day one. Magazine is a portal job (index route, featured, widgets), not a skin.
- You will not get a gaming HUD, a boxed card grid, or a vertical “esports” chrome without writing it.
- Brand-heavy marketing sites that must pixel-match a React homepage will spend more hours in extra.less than the RM ZIP would have cost.
Honest labour estimate (not a quote). A competent admin who already knows properties: an afternoon for logo + palette + both variations + email check. A first-time admin: a weekend, including the three-session matrix in the dark-mode article. A pixel-match to an existing marketing site: days, and you should ask whether the forum must match the marketing site or merely not embarrass it.
If the board is a discussion community with a logo, start here. Buy a parent only when you can name the thing Default cannot do.
Path B — premium parent (framework or one-shot)
Two different products share a shopping tab.
Frameworks
UI.X 2 (ThemeHouse) — marketed as an “Ultimate Theme Framework,” Resource Manager update 25 Jun 2026, light + dark, requires the UI.X add-on. You are buying a system: more templates, more options, a rebuild step, and an add-on you must keep compatible with XF 2.3.x.
XenBase (PixelExit) — a foundation style, RM update 28 Jan 2026. Smaller idea than UI.X: a base you child off, not a second ACP.
Community thread (Jun 2025) treating Bolt (PixelExit) versus UI.X 2 as a real buyer question is the right kind of question. It is not a ranking. It is “do we want a framework with an add-on tax, or a foundation we will paint ourselves?”
Framework TCO extras the ZIP price does not show:
- The add-on must be installed and updated with XenForo.
- Rebuild can hit too many open files on a cheap host. That is a host ticket or a CLI rebuild, documented in the cookbook.
- More options means more ways to customize the parent. Customizing the parent is how you lose the next vendor update. Child anyway.
- Exit cost is real. Re-parenting a heavily optioned child back onto Default is a project.
One-shot skins
These are looks. You import them, you child them, you hope the author still ships 2.3.x updates.
Resource Manager snapshot used for this series (Styles 2.x, figures as recorded):
| Style | Author | List price | Notes on the snapshot |
|---|---|---|---|
| Legend | ThemeHouse | $59.50 | Gaming. Updated 29 Jul 2026 |
| Solfege, Retro | DohTheme | $55 | 2.3.11 line; many DohTheme updates 29 Jun 2026 |
| Minimal | DohTheme | $40 | Same line |
| Cozy, Fury, Alt, Pad, Gamez, Lotus, Flow, MaterialXen, FluentXen, Tiles, Vigas, xenAwsome, Mere | DohTheme | $30 | Same line |
| Velqeris | Eggy | (check RM) | Newer 2026, dark purple/cyan |
| Marmaris | erkanshi | (check RM) | Newer 2026 |
| Uniform | Ehren | (check RM) | Wallpaper-focused. Updated 2 Sep 2024 — may lag 2.3 |
| Shades of Grey | Gator | (check RM) | Unmaintained since 2022. Do not start a new board on it |
This article will not invent a 2026 dollar price that was not on that snapshot. If the cell says “check RM,” check RM.
What a current one-shot wins.
- A finished look in an evening if you follow the checklist.
- Authors who actually ship 2.3.11 updates (the DohTheme line and Legend in that snapshot) are paying down your merge risk.
- Gaming / boxed / magazine chrome you would otherwise write.
What a one-shot loses.
- You inherit someone else’s
PAGE_CONTAINERopinions. Add-ons that assumed Default will need CSS. - Update cadence is the author’s. Uniform’s 2024 date is a warning, not a slur. Shades of Grey is a do-not-buy for a new install.
- Two complete styles instead of one style with variations is two outdated lists. Prefer a 2.3 package that documents default + alternate.
- Exit: if the author stops, you either freeze on that XF version’s look or you re-parent and re-do extra.less.
Framework versus one-shot, in one paragraph
Buy a framework when you know you will run several colour children, a lot of style options, and you are willing to own the add-on. Buy a one-shot when you want this look and you will keep a thin child. Do not buy a framework to get dark mode. Do not buy three $30 skins to A/B test in production.
Path C — commission a custom style
This is how you get a unique parent that matches a brand system no RM skin will ever ship. It is also how you get a unique merge queue.
What a competent commission should include, written in the statement of work:
- A child of Default or a clearly versioned parent they will update after XF point releases. Prefer they deliver a child plus TMS plus extra.less, not a fork of Master.
- Variations if you need light/dark — two palettes, not two styles.
- Style properties first, extra.less second, template modifications third. Direct template edits listed and justified.
- No Google Fonts CDN. Self-hosted files.
- A test pass: guest / Registered / staff, both variations, email style, mobile width, widgets, one page node, login.
- Who merges outdated templates after the next 2.3.x. If the answer is “you,” budget your hours. If the answer is “them,” you are buying a retainer, not a ZIP.
- Source you can export from the ACP. You must be able to leave.
What this path wins.
- Pixel-match to a brand the RM will not sell.
- A designer in the room for the first-screen decisions the portal article treats as architecture.
- Possibly less extra.less than a badly fitted one-shot.
What this path loses.
- You are the vendor now, unless you pay them to stay.
- Unique HTML is unique merge conflict.
- A designer who does not run XenForo will paint hex into extra.less and break the dark variation. Put the cookbook in the brief.
Money: what we can say, and what we must label
RM skins in the snapshot sit at $30–$59.50 for the one-shots named above. Frameworks are a product page you should read live (this article will not invent a UI.X 2 dollar figure that was not in the snapshot). XenForo’s own licence is a separate line — previous series notes from xenforo.com/purchase: license $195, extension $60/year; Cloud Starter $60 / Standard $100 / Business $250 per month, ex VAT, and those numbers change.
Custom design is not on the Resource Manager. Estimates, not quotes:
| Scope | A plausible order of magnitude (2026 freelance / small studio) | What that usually buys |
|---|---|---|
| Palette + logo + extra.less on a child | A day or two of a XenForo-literate freelancer | Path A done well |
| Child of a premium parent, brand fit | Several days | Path B + their hours |
| Unique parent, variations, portal chrome, written retainer | Weeks, sometimes more | Path C |
Those rows are order-of-magnitude estimates. A specialist who already ships XF styles will not bill like a general WordPress shop; a branding agency that has never opened the ACP will bill more and deliver hex. Get two written quotes. Do not use this table as a budget line in a grant application.
If someone quotes a custom parent for less than a week of their time and promises lifetime XF updates, read the statement of work twice. Lifetime updates are either a lie or a product — in which case you are back on Path B with one customer (you).
Decision filter
Five questions. If four point at the same path, take it.
- What can Default not do? If the answer is “dark mode” or “our hex on the header,” Path A. If the answer is “a boxed gaming index with this chrome,” Path B. If the answer is “must match this design system nobody sells,” Path C.
- Who merges templates next March? If nobody, Path A. If you will pay a vendor who is still shipping, Path B. If you will pay the original designer, Path C plus a retainer.
- How many add-ons assume Default? A portal, a listing grid, and a stream page on a unique parent is a CSS project. Price it.
- What is the exit? Path A: already there. Path B: re-parent when the author stalls (look at update dates). Path C: only if the contract delivers ACP-exportable styles and a child, not a black-box ZIP.
- Is this anger at the style, or at a neglected board? Dead onboarding and a 90-node tree will look bad in every skin. The configuration mistakes article is cheaper than Legend.
A sixth veto: do not buy a skin to get a feature. Live streams are not a theme. Server directories are not a theme. Those are the plugin comparison. A pretty card that still does not query FiveM is still a thread.
Three-year sketch (so the sticker stops winning)
Assume one public style, variations on, a modest add-on list, two XF minor upgrades a year, and one person who can open the ACP.
| Path A child-of-Default | Path B current one-shot | Path B framework | Path C unique parent | |
|---|---|---|---|---|
| Year 0 cash | $0 style | $30–$59.50 (named RM) | ZIP + required add-on (live RM) | Quote (days–weeks; estimate) |
| Year 0 labour | Afternoon–weekend | Evening + checklist | Longer: add-on + rebuild | Project |
| Years 1–3 cash | $0 style | Updates if the author includes them | Updates + add-on | Retainer or your hours |
| Years 1–3 labour | Merge your extra.less | Merge child after vendor + core | Merge + rebuild tax | Merge unique HTML |
| Exit | None | Re-parent | Re-parent, more options to unwind | High unless SOW was good |
| Risk | Low | Author cadence | Add-on + host limits | Designer disappears |
Add your XenForo licence / Cloud invoice to every column. It does not change the comparison.
If Path B’s author has not posted a 2.3 update (Uniform’s 2024 date, Shades of Grey 2022), move that column to “do not start here.” Historical Styles Factory storefront products (Empire, Vertiforo, FiveStyle) are discontinued. They are not a 2026 Path B. If you still run one, treat it as Path C without a retainer: child what you can, plan an exit onto Default or a living RM parent.
How to buy Path B without inheriting Path C’s pain
- Import as a new parent. Never overwrite Default.
- Immediate child. All extra.less there.
- Enable variations on the style you will serve if the package supports them. Do not run a light SKU and a dark SKU.
- Do not customize vendor options on the parent “just to see.”
- Walk the checklist three sessions.
- Budget one hour after every XF or vendor update for Outdated templates.
- Keep Default installed. The exit is a default-style flip plus CSS you must retune — not a mythic uninstall.
Community extra.less / TMS / child-of-vendor is the whole upgrade-safe method. Designer mode is optional and advanced. Most commissions should never enable it on production.
How to commission Path C without buying a museum
Put these lines in the email before anyone opens Photoshop:
- Target: XenForo 2.3, variations on, email style separate and light.
- Deliverable: child style + extra.less + TMS list + property changelog. No Master edits.
- Tokens, not hex, on any surface both variations share.
- Self-hosted fonts.
- Test matrix attached (the dark-mode article’s table is enough).
- Named person who merges the next two core updates, and a price for that if it is not you.
- You receive ACP export / XML you can re-import on staging.
If the designer wants to rebuild the forum as a static marketing page with a comments plugin, you are no longer buying a XenForo style. You are buying a different product. That is a stay-or-migrate conversation, not a theme invoice.
Worked examples
Hobby game board, two mods, Default plus a Discord widget. Path A. Spend the Saturday on palette and the listing fields. A $30 skin will not make the directory more honest.
Growing gaming community that wants a storefront look and already pays for ThemeHouse things. Path B, Legend or a current DohTheme gaming skin, child, variations. Do not commission a unique HUD in week one.
Company support forum that must share tokens with a design system. Path A first (properties can get surprisingly close). If legal/brand still fails the screenshot test, Path C with a retainer, not a one-shot RM skin you will fight.
Board still on a 2022 unmaintained parent. You are already on the expensive side of Path B. This quarter’s project is an exit to Default or to a 2.3.11 line, not a custom commission on top of the corpse.
What “updated Jun 2026” is actually buying
An RM date is not a review. It is a pulse.
- UI.X 2 updated 25 Jun 2026 means the framework is alive on the 2.3 train. You are still buying the add-on and the rebuild.
- XenBase updated 28 Jan 2026 is alive enough to consider, quieter than a June date. Read the last discussion thread, not only the banner.
- Legend updated 29 Jul 2026 at $59.50 is a current one-shot in the gaming aisle.
- DohTheme 2.3.11 line, many at $30–$55, cluster of updates 29 Jun 2026 is a living catalogue. Pick a look, not a brand loyalty.
- Uniform, 2 Sep 2024 may lag 2.3. Ask in the resource thread whether variations exist before you pay.
- Shades of Grey, last 2022 is a museum. Do not start a new community on it.
Bolt versus UI.X 2 (community, Jun 2025) is the right buyer question for people who already know they want a system: PixelExit foundation versus ThemeHouse framework. It is not “which is best.” It is which add-on tax and which option tree you will live in.
Newer 2026 names in the same snapshot — Velqeris (Eggy), Marmaris (erkanshi) — are one-shots until they prove a second year of updates. Treat them like any new resource: child immediately, keep Default installed.
Historical Styles Factory products (Empire / Dark Empire, Vertiforo, FiveStyle) are discontinued storefront looks. They are not a 2026 Path B. If a 301 still points an old product URL at a portal article, that is a mapping job, not a reason to hunt a ZIP.
A worked three-year cash sketch (labels matter)
Assume self-hosted XF you already licensed. Style line only. Estimates where marked.
| Year | Path A | Path B one-shot (Legend $59.50) | Path B framework | Path C (estimate) |
|---|---|---|---|---|
| 0 | $0 + a weekend | $59.50 + an evening + checklist | ZIP + UI.X add-on (live RM) + longer first week | Designer hours: estimate days–weeks |
| 1 | Merge your child after core updates | Merge after vendor + core | Merge + rebuild + add-on update | Retainer or your unique merge |
| 2 | Same | Same, if the author still ships | Same | Same |
| 3 | Same | Exit if the date goes stale | Exit is heavier | Highest exit unless SOW delivered a child |
Add the platform TCO licence / Cloud / VPS lines to every column. They do not change the style comparison. They do remind you that a $30 skin is not the invoice that matters.
If Path C’s quote is lower than Legend and includes “lifetime XF updates,” you are either getting a Path B product with one customer, or you are getting a promise. Put the update obligation in writing.
What this is not
It is not a ranked “best of” list. UI.X 2 versus XenBase versus Legend is a fit question, not a score. It is not a shop. Historical Empire / Dark Empire / Vertiforo / FiveStyle SKUs are not for sale here. It is not a Core Web Vitals bake-off — a heavy slider is a portal and speed problem on every path.
If you already bought the ZIP, stop comparing. Open the checklist and import it as a parent.
Takeaways
- Child-of-Default is the cheapest honest TCO for most boards. 2.3 variations are included.
- Premium is either a framework (add-on + rebuild tax) or a one-shot ($30–$59.50 in the named RM snapshot). Update date matters more than the demo.
- Custom is hours plus a merge owner. Label any day-rate as an estimate; get a statement of work that delivers a child, tokens, and an exit.
- Do not buy a skin for dark mode, listings, or streams.
- The expensive style is the one nobody will merge.
Pick the path you can still upgrade in 2028. Then go take the backup you should have taken before you imported anything.