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
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:
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.
Supporting neutrals:
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.
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.
- 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:#partnerships) before publishing.
Press inquiries
For press, partnership, or media materials beyond what’s in this kit:- Discord — discord.gg/raydium,
#partnershipschannel. - X / Twitter — @Raydium.
Address
c/o MetaBase58 Cayman Limited of 71 Fort StreetPO Box 10035
George Town, Grand Cayman KY1-1001
Cayman Islands
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
resources/community-tools— third-party tools that integrate with Raydium.resources/license— licensing terms (separate from trademark).security/disclosure— for security disclosures, not press.
- Raydium docs theme configuration (canonical brand colors).
- Raydium GitHub organization — master logo files.

