Press and media kits
A press kit page journalists can actually use.
Journalists, podcast hosts and partners want the same things: the logo in a usable format, the right colors, a description they can quote and someone to contact. GitBrand gives you a press kit page with all of it, without building a page from scratch.
Public page · indexable · no account needed to download
SVG is the source. PNG and JPG are exported on demand for tools that cannot place vectors.
What to include
Complete for someone with ten minutes.
A press kit does not need to be long. It needs to answer every question in the ticker above without a reply from you. Each item maps to a section of a GitBrand repository.
Logo in SVG, plus PNG on light and dark
Upload the SVG once; GitBrand exports PNG and JPG for the tools that cannot place vectors. Add the dark-background version as its own variation.
→ Logos sectionBrand colors with HEX values
On-screen graphics, lower-thirds and article illustrations match when the writer can copy the exact value instead of eyedropping a screenshot.
→ Colors sectionA short description and a boilerplate
Two sentences a writer can paste, and a longer paragraph for the end of a press release. Put them in the repository description and the FAQ.
→ Description + FAQScreenshots, founder photos, awards artwork
Each resource is a downloadable file with a name and a description, so a photo carries its own credit line and usage note.
→ Resources sectionUsage notes
Minimum size, clear space, what not to do. Keep it short; a press kit is read in the ten minutes before a deadline.
→ FAQ sectionA contact for press enquiries
The website link and contact email sit in the repository header, above the fold, on every visit.
→ Repository headerPress kit vs media kit
The terms overlap. The audiences do not.
Both are a public GitBrand repository. The difference is who opens it and what they expect to find.
| Aspect | Press kit | Media kit |
|---|---|---|
| Audience | Journalists, editors, podcast hosts, conference organisers | Advertisers, sponsors, partners evaluating a placement |
| Purpose | Make it easy to write about you accurately and quickly | Make it easy to decide whether to buy space or sponsor |
| Core contents | Logo, colors, boilerplate, product images, founder photos, contact | Everything in the press kit, plus audience figures, rate cards, formats |
| Tone | Factual; quotable sentences | Persuasive; numbers and proof |
| In GitBrand | Logos, Colors, Resources and FAQ sections of a public repository | The same repository, with rate cards and audience decks added as resources |
| If you need both, one public repository usually covers it. Keep the internal brand kit member-only and publish the approved subset. | ||
Publish it
Three steps to a /press link.
No page builder. The repository is the page; you only decide where to link it from.
Create a public repository
Name it after the company and write a two-sentence description a writer can paste. Add your website and contact email.
gitbrand.com/your-companyAdd the assets
Upload the logo in SVG. GitBrand exports PNG and JPG for the tools that need them. Add product screenshots and founder photos as resources with credit lines.
Logos · Colors · Resources · FAQLink it as /press
Add the repository link to your site footer, your email signature and your outreach. Embed it on your own domain if you prefer to keep visitors there.
yoursite.com/press → gitbrand.com/embed/your-companyAI assistants
Make the facts readable by machines too.
Writers increasingly ask an AI assistant for a company's brand facts. Give it the approved version.
If you enable AI access on a public repository, GitBrand publishes the same kit as brand.json, a Markdown brief, llms.txt and llms-full.txt, a REST endpoint and an MCP endpoint. Assistants and agents that respect those files get your description, palette and links instead of a guess assembled from third-party uploads.
Password-protected and member-only repositories are excluded from every AI surface. The switch is per repository, so a public press kit can be AI-readable while the internal brand kit stays private.
gitbrand.com/north/brand.jsonStructured recordgitbrand.com/north.mdMarkdown briefgitbrand.com/north/llms.txtIndex for assistantsgitbrand.com/api/v1/repos/northRESTgitbrand.com/mcp/northMCP endpoint
FAQ
Before you send the first link.
Can journalists download the logo without signing up?
Yes. Public repositories are open to anyone with the link and require no account. Logos download as SVG, PNG or JPG directly from the page.
Can I include photos and PDFs?
Yes. Add them as resources. Each resource is a downloadable file with its own name and description, which is where a photo credit or usage note belongs.
Should the press kit be a separate repository from our main brand?
Often it is the same repository. If your internal brand kit contains material you do not want public, keep that member-only and create a separate public press kit with the approved subset. The Free plan includes up to five repositories.
Can I host the press kit on my own domain?
On the Free plan the kit lives at gitbrand.com/your-slug and can be embedded on your site via gitbrand.com/embed/your-slug. Custom domains and removing GitBrand branding are part of the Premium plan.
How do I know if anyone uses it?
Open Insights in the editor: views over time, unique visitors, referrers, countries and download counts per logo or file. You will see that the press kit is used and which assets travel, not which journalist took them.
Related: For startups · Logo file formats explained · The ideal logo package