Skip to main content

Anise vs Licorice: shared flavor compounds

8 of 306 flavor compounds are shared (Jaccard 0.03) — the molecular basis for whether Anise and Licorice pair well or work as substitutes. Full side-by-side breakdown below.

1
2

Two ingredients gives the full side-by-side breakdown; add a third to see a similarity matrix across all of them (up to 6).

8
Shared
279
Anise reported
35
Licorice reported
0.03
Jaccard

“Reported” counts reflect the compounds characterized for each ingredient across the studies and databases we aggregate — a measure of coverage, not an exhaustive census. Different analyses target different compound classes and methods, so read these as what has been characterized, not the total number of molecules present. Jaccard measures shared coverage, so it rewards overlap rather than highlighting the ratio differences that distinguish two ingredients.

Why they pair: shared-compound network

8 of 8 shared shown

Each molecule in the middle is shared by both ingredients — the chemistry bridging Anise and Licorice. Node color is chemical class and node size is perceptual potency (bigger = lower odor threshold, so it drives aroma at smaller amounts); a copper ring marks compounds flagged as key aromas in published GC-O studies. Zoom with the +/− buttons or a pinch, drag the background to pan, drag a node to pin it, click any molecule for its full profile.

Where they differ: aroma character

Profile distance 0.37

The Jaccard above measures overlap; this compares each ingredient’s aroma-family mix side by side — the wider the gap between the two bars, the more that family sets the ingredients apart. Anise reads left, Licorice reads right.

13.6%
Other
0.0%
1.2%
Caramel
13.3%
6.4%
Roasted
13.3%
0.8%
Dairy
6.7%
8.8%
Green
3.3%
14.0%
Herbal
10.0%
16.0%
Sour
20.0%
10.4%
Fruity
6.7%
3.6%
Woody
0.0%
0.0%
Earthy
3.3%
Anise ◀ ▶ Licorice

Shares are fractions of each ingredient’s labeled compounds (249 of 279 for Anise, 30 of 35 for Licorice) — compositional lean, not concentration. Aroma labels come from our compound enrichment and cover most, but not all, characterized molecules.

Pro names the molecules behind each difference — the specific compounds in each aroma family that one ingredient has and the other doesn’t. Sign in to see them.

Published recipes using both

1 found

Real dishes from our 610K+ curated recipe corpus that combine anise and licorice — proof the pairing works in practice.

Shared compounds

8 of 306 total

These are the molecules both ingredients have in common — the chemistry behind why they pair. Grouped by chemical class; ★ marks compounds flagged as key aromas in published GC-O studies. Click any molecule for its identifiers (CAS, formula, PubChem CID), odor data, and every ingredient it’s found in.

Most perceptually potent shared compounds

8 of 8 shared are aroma compounds with a measured threshold

Odor threshold is the concentration at which a molecule becomes smellable — lower = more potent. These clear their threshold most easily, so they drive the shared aroma out of proportion to the raw shared count.

Showing the 6 most potent of 8 with measured thresholds. Sign in for the full ranked list.

Showing the 5 highest-impact of 8 shared compounds (key aromas first) — sign in for the full list, grouped by chemical class with key-aroma markers.

See 272 anise-only and 27 licorice-only compounds with Pro

Side-by-side ingredient comparison — including the unique compounds in each ingredient — is a Pro feature.

Try the pairing tools for full recipe-aware scoring, or explore anise's profile.

Cite this analysis
Plain text
Compound Kitchen (2026). Compound similarity analysis: Anise vs Licorice. https://compkitchen.com/compare?a=anise&b=licorice. Accessed 2026-09-29.
BibTeX
@misc{compkitchen_compare_compound_similarity_analysis_anise_vs_licorice_2026,
  title  = {Compound similarity analysis: Anise vs Licorice},
  author = {{Compound Kitchen}},
  year   = {2026},
  url    = {https://compkitchen.com/compare?a=anise&b=licorice},
  note   = {Accessed: 2026-09-29}
}

Methodology DOI: 10.5281/zenodo.19719459 · CC BY 4.0 · Citations are a request, not a requirement.