How to Build a Press Kit for a Web3 Project

A press kit is a small bundle of files and facts that lets anyone write or talk about your project without asking you for basics. Journalists use it, but so do podcast hosts, directory editors, partner teams, community ambassadors and the person designing a banner for your launch.

A good kit removes friction. When someone wants to mention you, they grab the right logo and the right description instead of a blurry screenshot and an outdated tagline.

Where to host it

Keep the kit at a stable, easy URL such as yourproject.com/press. Link it from your website footer and your docs. Avoid hosting it only in a shared drive that asks for access, because busy writers will not wait for approval.

Offer both a web page with the essentials and a single download containing all the files.

The facts section

Start with plain text people can copy:

• Project name with correct capitalisation
• One-sentence description
• One-paragraph description of around sixty words
• Longer description of around two hundred words
• Launch date and current status
• Supported chains and main contract addresses
• Official website and social links
• Contact method for media questions

Write the descriptions in the third person. Writers can paste them directly without rewording "we" into "they".

Logos and brand assets

Include your logo in formats that work in different places:

File	Use
SVG logo, full colour	Websites and print
PNG logo on transparent background, 1000 px	Slides and articles
Square icon, 512 px	Avatars, directory listings, map pins
Light and dark versions	Placing the logo on different backgrounds
Brand colours as hex codes	Designers building banners

Add a short note on how not to use the logo, such as stretching it or changing colours. Keep it friendly and brief.

Product visuals

Screenshots and short clips help people understand the product faster than any description. Include three to six clean screenshots at high resolution, showing the main flows. Remove test data, personal wallet addresses and anything embarrassing in the browser tabs.

If the product has a mobile version, include phone screenshots as well. A short screen recording of a transaction from start to finish is especially useful for podcasts and video creators.

Team and background

If your team is public, add short bios and headshots. If you work under pseudonyms, say so clearly and explain how people can verify official communications, such as through signed messages or links from the official site. Honesty here builds more trust than vague claims.

Include a short timeline of milestones with dates. Writers love a clear story of how a project got to where it is.

Facts that need care

Anything a writer might quote should be accurate and easy to check:

• User numbers, with the source and date
• Total value locked or volume, linked to a public dashboard
• Audit reports, linked to the auditor's page
• Funding or grants, only if the other party has confirmed publicly

If a number changes often, link to a live source instead of writing it in the kit.

Keep it current

Assign one person to update the kit after every major release. Stale kits cause old logos and wrong descriptions to spread across the internet, and they are hard to clean up.

Your press kit is also the source of truth for every listing you create. When you add your project to a directory or claim a tile on the Proud Globe, use the square icon and the one-sentence description from the kit so your project looks the same everywhere.