Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.raydium.io/llms.txt

Use this file to discover all available pages before exploring further.

This kit is what the project asks third parties to follow when displaying the Raydium name, logo, or visual identity. Following these rules helps users immediately recognise legitimate Raydium surfaces and avoid confusion with imitators.Master assets live in the docs repository under /logo/. If something here doesn’t match the master, the master wins.

Name and capitalisation

FormUse
RaydiumThe protocol name. Always title case. Never raydium, never RAYDIUM.
Raydium ProtocolAcceptable when disambiguating from the Raydium name in other contexts (it’s also a chemical, a video game, etc.).
$RAY or RAYRaydium’s native SPL token. With the dollar prefix in marketing copy, plain RAY in technical or table contexts.
Raydium AMM v4 / Raydium CPMM / Raydium CLMM / LaunchLabProduct names. LaunchLab is one word, capital L’s.
Burn & EarnOne construction with the ampersand, both nouns capitalised.
Don’t write Raydium DEX, Ray protocol, or Raydiums (no plural). The protocol is a singular noun.

Logos

The Raydium logo comes in two forms:
  • Wordmark — the full “Raydium” type lockup. Use this in headers, press materials, and any context where the name needs to be readable.
  • Symbol mark — the standalone monogram. Use this in app icons, favicons, and confined spaces (avatars, social profile pictures) where the wordmark won’t fit at a legible size.

Light and dark versions

Two finishes per form:
FileBackgroundUse when
logo-light.svgDark backgroundsPrimary placement on dark UI surfaces.
logo-dark.svgLight backgroundsPrimary placement on light UI surfaces.
mark-light.svgDark backgroundsSymbol-only on dark surfaces.
mark-dark.svgLight backgroundsSymbol-only on light surfaces.
All assets are vector SVG. Use SVG wherever possible. Rasterise to PNG only at the final render size (avoid scaled PNGs).

Clear space

Maintain clear space around the logo equal to the height of the Raydium “R” character. Don’t crowd the logo with text, icons, or graphics inside this margin.

Minimum size

Wordmark: don’t render below 120 px wide on screen, or 20 mm in print. Symbol: don’t render below 24 px wide on screen, or 6 mm in print. Below these thresholds the logo loses legibility and partners should switch to the alternate form (e.g. drop the wordmark for the symbol when space-constrained).

Color palette

The Raydium identity is built around a violet primary with darker and lighter variants for state, depth, and contrast.
RoleHexRGBUse
Primary#8C6EFF140 / 110 / 255Main brand color. CTAs, links, key accents.
Light#A88BFF168 / 139 / 255Hover states, secondary accents, light-theme backgrounds.
Dark#5E3BE194 / 59 / 225Active/pressed states, dark-theme accents, depth.
Supporting neutrals:
RoleHexUse
Foreground (light)#0A0A0FBody text on light surfaces.
Foreground (dark)#FAFAFABody text on dark surfaces.
Surface (light)#FFFFFFPage background, light theme.
Surface (dark)#0F0F1APage background, dark theme.
Border#E5E5EB (light) / #1F1F2E (dark)Card and divider borders.
Don’t recolor the logo. The wordmark and symbol are always rendered in either the light or dark master finish — never tinted, never gradient-replaced, never run through brand colors.

Typography

The docs and site use Inter for UI and body copy. Headings use Inter at heavy weights (600–800). Code blocks use JetBrains Mono or any monospaced fallback.
StyleFamilyWeightUse
Display / H1Inter800Page titles.
H2–H4Inter700Section headers.
BodyInter400Paragraph text.
EmphasisInter600Inline emphasis, strong text.
CodeJetBrains Mono400–500Inline code and code blocks.
Inter is open-licensed and available from rsms.me/inter.

Logo do’s and don’ts

Do:
  • Use the official SVG masters from the docs repo /logo/ directory.
  • Maintain clear space and minimum size.
  • Pair the wordmark with the symbol only when both are visually balanced (don’t show two side-by-side at conflicting sizes).
  • Render on a background that has sufficient contrast — use the light master on dark, dark master on light.
Don’t:
  • Recolor the logo. No purple wordmark, no rainbow, no monochrome variants beyond the supplied light/dark.
  • Distort the aspect ratio (no stretching, no skewing).
  • Add drop shadows, outlines, glow, or other effects.
  • Place the logo on a busy background image without a contrast-preserving solid panel underneath.
  • Crop the logo (don’t show only the “R” cropped out of the wordmark — use the symbol mark instead).
  • Use the logo to imply endorsement of a product Raydium hasn’t formally partnered with. Use a “powered by Raydium” or “integrated with Raydium” badge in a neutral context, with no implication of vetting.

”Powered by Raydium” badge

If your integration uses Raydium as a routing source or liquidity venue, a simple text or badge attribution is welcome:
Powered by Raydium
Integrated with Raydium
Liquidity via Raydium
These wordings are pre-approved. Place near the integration’s pricing, swap, or pool surface — not in masthead-prominent positions, which would imply formal partnership. If you’re an aggregator or wallet routing through Raydium and want a more prominent attribution, contact the team via Discord (#partnerships) before publishing.

Press inquiries

For press, partnership, or media materials beyond what’s in this kit: The team responds to press inquiries on Discord faster than DMs on social platforms.

Asset bundle

A zipped bundle of every logo file, color swatch, and font reference is mirrored on the Raydium GitHub. The canonical SVGs used by this docs site are at /logo/light.svg and /logo/dark.svg.

Pointers

Sources: