
Web3 branding: how to build a crypto brand people trust
Imran KhanNovember 18, 202616 min read

table of contents
Before anyone uses a Web3 product, they have to decide whether to trust it with money. The name, the logo, the words and the screens are what they see first.
This guide is about building the brand so that decision gets easier. We cover the strategy, the name, the mark, the colours and type, the voice, the claims you make, how to protect the brand from copies, and how to change it later without losing the people who already know it. It's written for founders of crypto and Web3 products and for the designers working with them.
One thing up front. We're a design studio, and we haven't branded a Web3 protocol. Our brand work is Recalin, which isn't a Web3 product, and our Web3 work is Reputable, where we designed the product and website. We'll use both for what they actually show, and lean on sources for the rest. Every outside fact is linked to the page it came from, read on 18 November 2026. Nothing here is legal or financial advice.
The short version
- In Web3, the brand is a trust signal first. Coinbound calls it the first signal people use to gauge whether you're serious.
- Make only claims people can check. If the brand says "community-owned" or "fair", the product, the governance and the token have to say the same.
- Draw the mark from the smallest size up. It will probably appear as an app icon, a favicon and a token image long before it is on a billboard.
- Check the name before you fall for it. Search, pronunciation, domain, handles and trademark, in that order.
- Your copy may count as a financial promotion. In the UK, crypto promotions have had to be clear, fair and not misleading since October 2023.
- Expect to be copied. Plan the official links page and the "we will never ask you to" list before launch.
- Write the rules down, with the "don'ts". Guidelines are what keep the brand intact when other people start building with it.
What's different about a Web3 brand
The agency guides that rank for this search agree on the main idea. Ramotion puts it as brand perception no longer living inside the company's control: it's shaped by the communities and contributors who use the product. Coinbound says the same thing from the trust side, that a brand is often the first signal people use to judge whether you're serious.
We agree with both. Two things follow that the guides spend less time on.
People meet the brand in places you don't control. Someone can meet a Web3 brand first inside a wallet, in a list of tokens, on an exchange, in a chat group or in a screenshot someone else posted. Here's what we'd design for.
| Where they meet it | What they see | What to design |
|---|---|---|
| A wallet or app picker | A small icon and a name | A mark that's clear at icon size, and a name that can't be confused |
| Token list or explorer | A tiny image next to a ticker | A version of the mark made for that size |
| Your app | Screens, numbers and warnings | The same colours, words and tone as everywhere else |
| Docs and community | Pages and chat | A voice that explains instead of hyping |
| Search results | A name and a link | A name that's unique enough that you come first |
A claim has to survive a check. Coinbound's example is useful: "using DAO language without giving holders real governance" loses trust fast, and so does pushing decentralization while the decisions are made behind closed doors. Whatever the brand says about itself becomes something people can test, so the brand and the product have to be the same story.
Start with strategy, and keep it short
Avark splits a brand strategy into three parts: the core (purpose, vision, values), the positioning (audience, market, competitors) and the personality (voice and tagline). Ramotion uses the same split. It's a sensible way to cover the ground, and you don't need a 40-page document for it.
Our own process, on the brand identity design page, starts with understanding the company: who you sell to, who you sit beside, and what the company has to be believed to be. It's founder interviews plus a look at everyone a buyer will compare you with, and it usually takes two to three days. That last phrase, "what the company has to be believed to be", is the useful one for Web3. Write it as one sentence a stranger could repeat.
Then do a claims audit. List every promise the brand is about to make, such as "secure", "fair", "community-owned" or "transparent". Next to each, write the thing a user could check to see it's true. A security audit report, a public vesting schedule, a governance vote that actually changes something. If there's nothing to put in the second column, cut the claim or build the thing.
Reputable, the Web3 developer reputation product we designed, ran on the same logic. Its case study says a score on its own is just a number, and people in that space have learned not to trust numbers, so every figure had to lead somewhere: to the commits behind it, the protocols it touched and the peers who vouch for it. That was a product rule, but it works as a brand rule too. Say less, and make each thing you say easy to check.
Choose a name you can keep
The name is the part of a brand that's hardest to change, and it's the one Web3 guides mostly skip. Before you commit, work down this list.
- Say it out loud. Read it to someone on a call. If they ask you to spell it, so will everyone else.
- Search it. Look at what comes up for the name alone and the name plus "crypto". If someone else owns the results, so will they own your traffic.
- Check the domain and the handles. You want the same name, or a very close one, on your site and on the social accounts people will look for. Copies of your brand are a real risk, which we cover below.
- Check the ticker if you'll have a token. Look for tokens with the same or a near-identical symbol, so nobody mixes yours up with another.
- Ask a trademark lawyer. Not us, and not a blog. The cost of a short check is small next to a forced rename.
The reason to take trademarks seriously is in the news right now. In September 2026, crypto.news reported that Unicoin sued Uniswap Labs in a New York federal court. According to the complaint, Uniswap's lawyers wrote in June demanding that Unicoin stop using names containing "UNI" in crypto and hand over two domains, and Unicoin says it has used its name since 2021 and that the two brands look and mean different things. We don't know how it ends, and these are one side's allegations. The part worth taking from it is that a name built on a short, common-sounding prefix in a crowded category can end up in a dispute.
Draw the mark from the smallest size up
Our argument, which Ramotion and Avark both touch on, is that Web3 products show the mark in small places you don't control.
Start with the spec for how browser wallets announce themselves to apps. EIP-6963 says a wallet's icon is passed as a data URI, and that the image "SHOULD be a square with 96x96px minimum resolution", with PNG, WebP or SVG recommended. That's a minimum for the source image, not a display size, and it covers only wallets that use that standard. Our reasoning is that an icon of this kind will be shown small, in a square, so your mark has to read as itself there, on light and on dark.
Avark makes the same point about tokens: a project that has its own token needs an icon that works at small scale, so skip anything too detailed or ambiguous.
The sketch above is the final mark. Here's how we got there on a project of ours. Recalin is a save-and-recall app, not a Web3 product, but the lesson carries over. Its case study says our first mark cut a looping arrow into the letter R, to suggest coming back to what you saved. It was clever, and too busy at the size of a home-screen icon. We kept the bookmark folded into the R, let the loop go, and, in the case study's words, the mark got stronger for it. Our service page puts the rule plainly: the small versions that actually get used, an app icon, a favicon, a profile picture, drawn to hold up at sixteen pixels before anyone judges the mark at full width.
So here's the test we'd run on any Web3 mark before signing it off:
- Show it at 16, 32 and 96 pixels, on light and on dark.
- Crop it to a square and to a circle, since you don't control how other apps frame it.
- Put it next to the marks of five competitors, at the same small size. If it blends in, it's not working.
- Remove the name. Can someone still tell which project it is?
One more example, because size rules are easy to get wrong. When Uniswap Labs put its proposed 2021 protocol rebrand to the community, the proposal came as a logo family in four sizes: Hero for billboards and posters, Primary for app icons and avatars, Micro for favicons and navigation, and Token for the token icon. Community members replied with sharp points. One said that having to change the logo at different sizes is an anti-pattern because third parties will certainly use the wrong size. Uniswap Labs replied that in practice the Primary mark would be used in almost all cases. So a size family can work, but it adds a rule people have to follow, and it needs to be in the guidelines and easy to download. The thread is the proposal and its comments, and we haven't found the outcome in it, so we use it for the questions it raised, not as a finished rebrand.
Colour and type that don't look like everyone else
Whatever look you choose, a look that many projects share can't tell people which one they're seeing, so check your shortlist against five competitors.
Our approach on Recalin was to choose from the neighbourhood the product lives in, not from the category. The case study says the brand had to sit closer to the apps people save from than to a productivity tool, so it used four colours (a soft near-white, a bright cyan, a clear azure and an electric indigo) with Aeonik for headlines and Satoshi for everything else. For a Web3 product the equivalent question is who your user is and what else is on their phone. A trader's screen and a first-time saver's screen shouldn't share a palette just because they share a blockchain.
Three practical rules. The first comes from Reputable, shown above:
- Design light and dark together. Reputable shipped in both. If your audience uses both, designing one and inverting it later is how you get washed-out charts.
- Check contrast. The WCAG contrast criterion, a Level AA requirement, asks for at least 4.5:1 for normal text and 3:1 for large text. Check it on your real backgrounds, in both themes.
- Pick one accent for actions. If every element glows, the button doesn't.
Give the brand a voice, and a jargon policy
Avark's tip for voice is a good one: imagine the brand as a person, then imagine that person writing all your copy. Ramotion adds the balance that's specific to this space, which is borrowing from Web3 culture, such as memes, informality and community language, while keeping things clear and professional.
We'd add one practical piece, a jargon policy. Decide up front which words you'll use unexplained, which you'll explain once and link, and which you'll never use. Gas, slippage, staking and bridge may be everyday words to your core users and unfamiliar to newcomers. The Web3 UX design guide goes deeper on the words inside the product.
Recalin's voice shows what a usable rule looks like. Its case study describes two beats, one for saving and one for finding: "Save now. Recall anytime." and "Capture today. Recall tomorrow." After two of them, it says, anyone on the team can write the third. A voice that's a pattern a stranger can continue is more useful than a list of adjectives.
Your copy is a promise, and in some places a regulated one
This is the section most brand guides leave out.
In the UK, the FCA's rules for promoting crypto to UK consumers have applied since 8 October 2023. Its announcement, first published in June 2023, says that adverts have to be clear, fair and not misleading, that promotions need clear risk warnings, that first-time investors get a cooling-off period, and that "refer a friend" bonuses are banned. It also notes that before the FCA took on this role, the UK's advertising regulator had already banned crypto promotions, including billboards telling people it was time to buy Bitcoin with no clear risk warning, and a football club's fan token promotion that was judged to have trivialised investing.
That's a 2023 announcement and rules change, and other countries have their own, so we aren't lawyers and you should check the current text. Take this as a reason to check, not as a guide to compliance. For a brand it means two habits. Put the tagline, the launch campaign and the landing page copy past someone who knows the rules for the places you'll be marketing. And write the brand voice so it never needs to promise returns, guarantees or urgency. That's better marketing as well as safer: Coinbound lists "overpromising with branding, underdelivering in mechanics" as the first pitfall, and warns that tokenomics which contradict the brand's values, such as claiming fairness while giving large early allocations to insiders, damage credibility.
Community: pick a few places and run them well
Most of the ranking guides put community at the centre. The advice we'd keep:
- Choose a few channels. Our suggestion is two or three, done well, with the official ones named.
- Treat the first visit as onboarding. Ramotion points out that community spaces need structure: clear onboarding for new members and organised channels.
- Show the brand to the community before you finalise it, but keep the decision. Coinbound suggests letting holders vote on visuals. Our view is that you ask people what confuses them and what they can't tell apart, and then the team decides. Feedback on clarity is useful, and a vote on taste usually isn't.
Expect to be copied
Because the brand is the first thing people judge, it's also something scammers copy.
On 1 October 2026, Malwarebytes reported finding 70 websites that impersonate legitimate crypto projects, and invite people to vote on the date of a rewards distribution. The pages copy the real sites "down to the logo, menus, and colors", and the Vote button opens a wallet connection prompt. The projects copied include xStocks from Kraken, Pendle, Zama, Kinetiq and others. Malwarebytes notes none of the pages are affiliated with them, and that the targets look chosen because their communities are used to hearing about rewards, claims and allocations.
You can't stop a copy from being made. Malwarebytes's own advice is to check the address, not the design, since branding alone can't show a site is genuine. What follows is our judgement, not an established standard, on what to put in the brand system before launch to help with that:
- One official links page, on your main domain, listing every real site, app store listing and social account. Link to it from everywhere.
- A "we will never" list in your voice rules. For example, never ask users to connect a wallet to claim something, never DM first. Say it in the docs, in the community welcome message and in a pinned post.
- A fixed way of announcing things. If rewards or claims are always announced in the same place and the same format, an announcement that arrives some other way is easier to doubt.
- Consistent domains. Don't launch a campaign on a new throwaway domain, because it teaches your users that odd domains are normal.
None of these is a design trick. They're brand decisions, because they decide what your real thing looks like when someone is trying to tell it from a fake.
Write the guidelines, including the "don'ts"
925Studios is the guide in the top five that treats guidelines as something developers use: it covers design tokens, component rules, ownership, versioning and handoff. We'd follow that approach. A guideline that's a PDF of logos doesn't stop a developer from using the wrong purple.
For a public example of the end result, look at the ethereum.org brand assets page. It offers the Ethereum diamond as a glyph and in gray, colour and purple, as logos in portrait and landscape, as a wordmark, and in versions for transparent and for solid backgrounds. Someone who needs the mark gets the right file for the surface instead of recolouring it. The five steps on our service page work for a Web3 brand as well:
- Understand the company. Founder interviews, and the brands a buyer will compare you with.
- Set the direction. Two or three routes, each a real argument about how the company should read, shown on the surfaces that matter. You pick one and we stop showing the others.
- Build the identity. Logo, type, colour and iconography, tested in an app icon and a product screen before sign-off.
- Write it down. Guidelines, brandbook and tokens, including what not to do, "which is the half most brandbooks leave out."
- Roll it out. Deck, site, store assets and social, launched together.
Our service page says a brand that arrives everywhere at once reads as deliberate, and one that leaks out over a month reads as unfinished. That's our view as a studio. Recalin's identity, from the first sketch to the launch campaign, took six weeks, and it launched with the whole identity in place from day one. If you're planning a Web3 identity, our brand identity design page shows how we scope it: a written scope and a fixed price.
When you need to change it
Sooner or later, a Web3 brand has to change: the project grows, splits or pivots. The best-documented example is public. In November 2021, Uniswap Labs proposed an update that would separate the look of Uniswap Labs and the Uniswap Protocol. It published the assets and a questionnaire, said it would ask for feedback over the following week, and announced a presentation and open feedback session for 10 November.
The replies are worth reading as a lesson in what a community protects. Several people agreed the split made sense but said the existing logo was distinctive and that they'd rather the company rebrand than the protocol. Others worried the new mark was too complex. The comments we quote were mostly about recognition people already had.
Our service page makes the same distinction. A brand refresh keeps what people already recognise and fixes what's failing, such as the type, the palette or how the mark behaves at small sizes. A rebrand is right when the company is genuinely a different business now, or the name itself is the problem. In Web3, where a community is attached to the mark, we'd start with the refresh and ask for evidence before going further.
How to tell whether it's working
Coinbound and Ramotion both list community and on-chain signals: sentiment, retention, active contributors, wallet activity. Those are all reasonable. Here are some simpler checks that are our own suggestions and cheap to run:
- Can a new person say what you do after ten seconds on the home page? Ask five.
- Do support questions repeat? If many people ask "is this the real site?", the brand isn't doing enough to tell them.
- Does the mark still read in a wallet, a list and a tab? Check at each release.
- Are the guidelines being used? If partners send you off-brand logos, the download page is hard to find.
What we've done and what we haven't
The pictures in this article are from our Recalin and Reputable case studies. Recalin is a brand identity project for an app that isn't Web3. Reputable is a Web3 product that we designed in dark and light over three months, working alongside its founding team. The case study covers the product and the website, and we don't claim its naming or logo.
We haven't branded a crypto protocol. What we bring is the process above, the habit of testing a mark at the size it'll really be used, and the habit of designing the product and the brand so each backs the other up. If you need a studio that has named and launched a token, ask any studio for that exact work, ours included. Our list of Web3 design agencies compares who else does this. The crypto app design guide covers the product side, and our pricing page shows how we work with product teams.
FAQ
It's the strategy, name, identity and voice of a project built on blockchain technology. The difference from ordinary branding is that people meet the brand in places you don't control, such as wallets and token lists, and that its claims can be checked against the product.
Ramotion's comparison is about control: traditional brands are managed inside the company, and Web3 brands are shaped partly by the community. In practice that means the brand has to hold up in small icons, community chats and public checks, not only on a website.
Write down what the project has to be believed to be, audit every claim, choose a name you've searched and checked, draw the mark from the smallest size up, set a voice and a jargon policy, write the guidelines with the "don'ts", and plan for copycats before launch.
Simple enough to read as a small square. The EIP-6963 standard for browser wallets asks for an icon that's square and at least 96 by 96 pixels as a source image, and tokens and favicons are likely to be smaller still. Test it at 16, 32 and 96 pixels on light and dark.
Say it aloud, search it, check domain and handles, check the ticker, and ask a trademark lawyer. A name that looks fine can still be someone else's.
Not necessarily. A clear brand gives a community something to gather around, and the community can then give feedback on it. Ask for feedback on what confuses people, and keep the final decision with the team.
Logo and its small versions, colour, type, voice and jargon policy, tokens for developers, the official links, a "we will never" list and a list of things not to do.
We can build the identity, guidelines and launch assets, and we've designed a Web3 product. We haven't named or launched a protocol, so ask us for the exact work you need.
If you're building a Web3 product and want the mark, the guidelines and the launch assets made together and tested at the sizes they'll really be used, book a call. Our brand identity design work covers the identity from the first sketch to the rollout.
About the author
Imran Khan, Founder & Creative Head
15 years of industry experienceFormer Head of Design at Day TranslationsFormer Creative Lead at SupersideWork at Superside for brands including Meta, Red Bull and Ray-Ban

related articles
Book a call
Pick a time that suits you
Get in touch
Let’s build something amazing together
Let’s build somethingamazing together
For product, interface and web-system work that needs clear direction and careful execution.





