AO3 work skin vs site skin vs public skin: which do you need?
AO3 has two kinds of skin: work skins and site skins. “Public skin” sounds like a third choice, but it is not. Public only means AO3 has approved a skin for other users to find and apply. A public skin is still either a work skin or a site skin, and it still follows that type’s rules.
The short answer: choose a work skin when readers need to see special formatting inside your fic. Choose a site skin when you want AO3 itself to look different on your own device. Choose from the public skins lists when an approved skin already does what you need.
Work skin vs site skin vs public skin
| Choice | Who sees it? | Where does it go? | What does it style? | Setup cost |
|---|---|---|---|---|
| Work skin | Readers of that work, unless they disable Creator’s Style | Saved under My Work Skins, then selected on the work under Associations | The contents of one fic: texts, tweets, letters, footnotes, special typography | CSS once, plus matching HTML in the chapter |
| Site skin | Only you, while signed in | Saved under My Site Skins, then chosen in your preferences or with Use | AO3’s interface on your devices: colours, fonts, spacing, tags, cards and navigation | Choose an existing skin or save CSS once |
| Public skin | Depends on its real type: site skins affect the user who selects them; work skins affect the work using them | Public Site Skins or Public Work Skins | Whatever its underlying type styles | Lowest if an approved skin already fits; select it instead of creating your own |
Where each choice lives on AO3
Start from your AO3 Dashboard and choose Skins. The page separates My Site Skins, My Work Skins, Public Site Skins and Public Work Skins. Those four tabs are two skin types crossed with two availability states: yours or public.
Where a work skin goes
Create or save the CSS under Dashboard → Skins → My Work Skins. Then edit the fic, open Associations, and choose it under Select Work Skin. The CSS supplies the design; the chapter still needs HTML whose classes match that CSS.
Where a site skin goes
A site skin changes your own reading interface. Save one under My Site Skins and choose Use, or select an available skin in Preferences → Your site skin. Other readers do not inherit it, and it does not travel with a fic you post.
A work can use only one work skin
Work skins do not stack. The work editor has one Select Work Skin choice. Selecting another replaces the earlier choice; AO3 does not combine both stylesheets for you.
If chapter 2 uses text messages and chapter 8 uses tweets, two separately selected skins are not the answer. Put both sets of CSS into one work skin, or use a master skin that already contains both. The AO3 social-media scene builder can export one master work skin covering its iMessage, WhatsApp, X/Twitter and Google scenes.
The same constraint matters when your fic already has custom formatting. Do not replace that skin and assume its rules survive. Merge the new CSS into the existing skin, check for class-name collisions, and preview old and new chapters before saving.
“Public” describes availability, not visibility
A public site skin does not make your personal theme visible to everyone. It means the approved skin appears in AO3’s public site-skin list so other logged-in users can choose it for themselves. Each person still decides whether to use it.
A public work skin is likewise an approved reusable work skin. Authors can select it on a work, but it does nothing to unrelated works. Saving your own private skin also does not automatically publish it: AO3’s public lists are approved collections, not an open gallery where every saved stylesheet appears.
For most authors, “public or private?” is therefore the second question. First decide whether the CSS is meant to change a fic or your own AO3 interface. Then check whether a public skin already meets the need before creating a personal one.
Which one should you choose?
- Your readers need to see the design inside the story: use a work skin.
- You want dark mode, different fonts, calmer colours or a denser AO3 layout: use a site skin.
- You want an existing approved design: browse the public list for the correct type.
- You need several kinds of formatting in one fic: combine them in one work skin.
If you want to build your own reading theme without writing CSS, the AO3 site-skin builder creates editable light and dark themes. If the design belongs inside a chapter instead, use the work-skin route above.
What happens when a reader turns Creator’s Style off?
AO3 applies a work skin by default, but readers can disable custom work skins. Downloads also do not retain the work skin. That is why a work skin should improve presentation without becoming the only thing making the chapter understandable.
Keep names, reading order and essential meaning in the HTML. A fake text conversation should still identify who said each line. A decorative divider should not be the only indication that time passed. The published examples The Arrangement and Sent to the Wrong Chat demonstrate that approach: the styled scenes resemble their platforms, while the unstyled chapter remains readable.
Two useful next guides
Once you know you need a work skin, the AO3 Twitter work-skin guide shows the CSS-and-HTML split in a complete example. If you are writing CSS yourself, check the reference to every CSS property AO3 allows before debugging a stylesheet the sanitizer will reject.
Sources
AO3 SkinGen is an unofficial fan tool and is not affiliated with the Organization for Transformative Works or Archive of Our Own.
