Hardware and timing
Consumer-ready olfactory hardware does not exist yet. Theme parks have run niche "4D" presentations, and a handful of startups are actively developing the technology, but nothing is shipping to end users. One startup claims availability within the year, a promise worth treating with the usual skepticism applied to launch dates.
History also offers a caution: Smell-O-Vision did not catch on. The CSS Olfactive API is moving forward regardless.
Which smells are allowed
The CSS Working Group has debated whether to restrict the API to fragrances the perfume industry considers broadly pleasing, or to open the web to a wider variety. Food-based smells such as fresh baked bread are pleasing but fall outside that narrow selection, and food advertisers would like them included. As it stands, the API supports only the twelve general categories used by the perfume industry, but the design allows for additional smells in the future—similar to how the color gamut can be expanded—provided more fragrance fragments become available.
Scent families and identifiers
The API draws on the Scent Wheel, also called the Fragrance Wheel, which groups smells into four larger families: Floral, Amber (previously called Oriental), Woody, and Fresh. Those are subdivided further, with some overlap between the large families and their sub-families:
- Floral:
- Floral (
fl) - Soft Floral (
sf) - Floral Amber (
fa)
- Floral (
- Amber:
- Soft Amber (
sa) - Amber (
am) - Woody Amber (
wa)
- Soft Amber (
- Woody:
- Woods (
wo) - Mossy Woods (
mw) - Dry Woods (
dw)
- Woods (
- Fresh (
fr):- Aromatic (
ar) - Citrus (
ct) - Water (
ho) - Green (
gr) - Fruity (
fu)
- Aromatic (
A scent is composed by mixing amounts of these fifteen categories using their two-letter identifiers. Fresh is the only large family with an identifier of its own (fr); the others are duplicated in their sub-families.
Markup
The API is implemented in HTML following the video and audio model: a new <scent> element, with <source> again used to offer the browser different options. Three competing formats are in development: .smll, .arma, and .smly—from Google, Mozilla, and Frank's Fine Fragrances respectively, the last of which intends to claim this "fourth dimension of the web."
<scent controls autosmell="none">
<source src=“mossywoods.smll” type=“scent/smll”>
<source src=“mossywoods.arma” type=“scent/arma”>
<source src=“mossywoods.smly” type=“scent/smly”>
<a href=“mossywoods.smll”>Smell our Mossy Woods scent</a>
</scent>
For accessibility, set the autosmell attribute to none. In theory this is not required, but some current hardware has a bug that activates the wafter even when no smell has been triggered.
The scent-profile property
As with background images and videos, a scent profile can be attached to an element through the scent-profile property, which accepts one of three things.
The keyword none, which is the default:
scent-profile: none;
A url() function pointing at a file:
scent-profile: url(mossywoods.smll);
Or a set of aromatic identifiers passed to the scent() function:
scent-profile: scent(wo, ho, fu);
That produces a scent with woody, water, and fruity notes—described to the author as "an orchard in the rain," though it read to him as "a wooden bowl of watered-down applesauce."
Up to five sub-families can be combined at once. The limit is arbitrary, but more would likely muddle the result. Each contributes equal amounts by default; the new whf unit adjusts the proportions. 100whf is the maximum potency of an aroma, and unlike most units the values must total 100whf or less. Anything beyond that is ignored—the browser takes the first 100whfs it encounters.
scent-profile: scent(wo 20whf, ho 13whf, fu 67whf);
Scaling the whole scent down means using values that add up to less than 100:
scent-profile: scent(wo 5whf, ho 2whf, fu 14whf);
If additional fragrances are permitted later, they would only require new fragrance fragments from which to build the aromatic mixture.
One profile per subtree
The working group's main concern was developers plastering scent-profile across every element, overwhelming users and blurring each scent into the next. The chosen rule: the browser permits only one scent-profile per the parent element's subtree. Once a profile is set on an element, neither its descendants nor its siblings can carry one. Profiles set on hungry selectors such as * or div therefore generate far fewer scents than they otherwise would. The restriction is easy to circumvent deliberately, but it is meant to stop a developer from accidentally overwhelming the user.
Accessibility and support
Because aromas can overpower, the API ships with a media query for detecting (and respecting) user preference:
.reeks {
scent-profile: scent(fl, fa, fu);
}
@media (prefers-reduced-pungency: reduce) {
.reeks {
scent-profile: scent(fl 10whf, fa 10whf, fu 10whf);
}
}
@media (prefers-reduced-pungency: remove) {
.reeks {
scent-profile: none;
}
}
Browser support is thin. Chrome—named for a bird that would smell gas in a mine—has not begun experimenting with the API, even in Canary. As of this writing, the KaiOS Browser is the only place to test it.



