• Product
  • Pricing
  • Docs
  • Using PostHog
  • Community
  • Company
  • Login
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Offsites
    • Security
    • Brand assets
      • Team structure
      • Why Small Teams
      • Team App East
      • Team App West
      • Team Platform
      • Team Ingestion
      • Team Infrastructure
      • Team Marketing
      • Team Website and Docs
      • Team People and Ops
      • Team Customer Success
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Releasing a new version
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • Breaking glass to debug PostHog Cloud
      • Developing the website
      • MDX setup
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Scale features prioritization
    • Paid features
    • Releasing as beta
    • Overview
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Offsites
    • Security
    • Brand assets
      • Team structure
      • Why Small Teams
      • Team App East
      • Team App West
      • Team Platform
      • Team Ingestion
      • Team Infrastructure
      • Team Marketing
      • Team Website and Docs
      • Team People and Ops
      • Team Customer Success
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Releasing a new version
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • Breaking glass to debug PostHog Cloud
      • Developing the website
      • MDX setup
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Scale features prioritization
    • Paid features
    • Releasing as beta
    • Overview
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
  • Handbook
  • How we work
  • Brand assets

Brand assets

Last updated: Sep 07, 2022

On this page

  • Logo
  • Typography
  • Building for web
  • Developing locally
  • Designing on desktop
  • Colors
  • Use opacity over more colors
  • Aesthetic
  • Buttons
  • Icons
  • Presentations
This page currently refers only to this website (posthog.com). It will later be updated to also include information about app.posthog.com.

Logo

If you're looking for the PostHog logo, you came to the right place. Please keep the logo intact. SVG is always preferred as it will infinitely scale with no quality loss.

PreviewNameVectorPNGPNG w/ padding*
Standard logoSVGPNG | PNG @2xPNG | PNG @2x
Dark logoSVGPNG | PNG @2xPNG | PNG @2x
Light logoSVGPNG | PNG @2xPNG | PNG @2x
LogomarkSVGPNG | PNG @2xPNG | PNG @2x

*PNGs with padding are useful when uploading the logo to a third-party service where there is limited control over padding/margin around the logo.

The @2x version of PNGs are designed for hi-dpi (or "Retina") screens. When using the logo in third party services that support uploading multiple versions (standard and hi-dpi), please be sure to include the @2x logo as it will appear crisper on newer devices, tablets and high resolution mobile devices.

If you have any questions or need clarification about which version to use, ask Cory, or reach out in the PostHog Users Slack and we'll be happy to help.

Typography

We use Displaay's typeface called Matter SQ. (SQ = square dots)

Building for web

On posthog.com, we use the variable font version. This allows us to specify our own font weights, which we do for paragraph text.

Context: Matter Regular's weight is 430 and the next step up is Matter Medium at 570, so we use our own weight of 475 for paragraph text.

Developing locally

Fonts are hosted outside of our posthog.com GitHub repo (due to licensing reasons). To protect the font files, they are restricted to loading on posthog.com and are not currently used for local development. Contributors will see the system default font load in place of Matter.

Workaround for local development

Restricted to PostHog employees, it's possible to reference the font locally to see an exact replication of what will be published on posthog.com.

Layout.scss contains some commented out code which can be used, in conjunction with the variable webfont files (restricted to PostHog organization members). Here's how to use them:

  1. Download the webfont files from the zip above
  2. Extract the files and place them in /public/fonts
  3. In Layout.scss, comment out the src for both fonts with production (Cloudfront) URLs and uncomment the relative URLs.
  4. Optionally use .gitignore to keep the files locally without inadvertently checking them in

Note: When submitting a PR, be sure to revert changes made to Layout.scss

Designing on desktop

We use 4 cuts of Displaay's Matter SQ typeface (SQ stands for square dots):

  1. Bold (titles and section headers)
  2. Semibold (paragraphs accompanying headers and paragraph links)
  3. Regular & Regular Italic (paragraph text)

Note that Regular and Regular Italic are lighter than the font-weight we use on the web, so paragraph text in Figma mockups will look noticeably thinner than how it appears on posthog.com.

When designing ads or other content with non-paragraph text, use Semibold instead of Regular.

We have a handful of licenses for desktop use of Matter. Contact Cory if you need the desktop fonts (OTFs).

NameWeightSizeLetter spacingLine height
h1Bold64px-1%100%
h2Bold48px-1%120%
h3Bold30px-2%140%
h4Bold24px-2%
h5Semibold20px-2%
h6Semibold16px0
Paragraphs accompanying large headersSemibold20px-1%125%
pRegular17px175%
p (small)Regular15px150%

Colors

We have two color schemes (light and dark mode), but primarily use light mode.

We use the same set of colors, and only swap out a couple hues depending on the color scheme.

Colors denoted with an asterisk (*) are the same between palettes.

NameLight modeDark mode
Text color (at 90% opacity)■ #151515■ #EEEFE9
Background color■ #EEEFE9■ #151515
Accent■ #E5E7E0■ #2C2C2C
Dashed divider line■ #D0D1C9■ #4B4B4B
Red*■ #F54E00
Yellow■ #DC9300■ #F1A82C
Blue*■ #1D4AFF
Gray*■ #BFBFBC
LinksUse Red

Use opacity over more colors

When possible, use opacity to modify colors. This allows us to use fewer colors in our palette, which is light years easier when working with two color schemes.

Paragraph textrgba($value, 90%)
Linksrgba($value, 95%) (and semibold)
Links:hoverrgba($value, 100%) (and semibold)

Aesthetic

Buttons

Use fully rounded buttons and centered text.

NameLight color schemeDark color scheme
PrimaryBackground: ■ #151515
Text: ■ #EEEFE9
Border: 2px ■ #151515
Background: ■ #EEEFE9
Text: ■ #151515
Border: 2px ■ #EEEFE9
SecondaryBackground: transparent
Text: ■ #151515
Border: 2px #151515, 10%
Background: transparent
Text: ■ #EEEFE9
Border: 2px ■ #EEEFE9, 10%

Icons

Use filled in icons over outlined icons.

Presentations

We use Pitch for polished presentations (like when giving a talk). Read more about this in our communication guidelines.

Questions?

Was this page useful?

Next article

Team structure

Reporting structure James Hawkins, CEO & Co-founder Tim Glaser, CTO & Co-founder Marius Andra, Full Stack Engineer Ben White, Full Stack Engineer Emanuele Capparelli, Growth Engineer Michael Matloka, Full Stack Engineer Paul D'Ambra, Full Stack Engineer James Greenhill, Data/Infra engineer Guido Iaquinti, Site Reliability Engineer Tiina Turban, Full Stack Engineer Yakko Majuri, Full Stack Engineer Eric Duong, Full Stack Engineer Alex Kim, Full Stack Engineer Li Yi Yu, Full Stack Engineer Neil…

Read next article

Share

Jump to:

  • Logo
  • Typography
  • Building for web
  • Developing locally
  • Designing on desktop
  • Colors
  • Use opacity over more colors
  • Aesthetic
  • Buttons
  • Icons
  • Presentations
  • Questions?
  • Edit this page
  • Raise an issue
  • Toggle content width
  • Toggle dark mode
  • About
  • Blog
  • Newsletter
  • Careers
  • Support
  • Contact sales

Product OS suite

Product overview

Analytics
  • Funnels
  • Trends
  • Paths

Pricing

Features
  • Session recording
  • Feature flags
  • Experimentation
  • Heatmaps

Customers

Platform
  • Correlation analysis
  • Collaboration
  • Apps

Community

Discussion
  • Questions?
  • Slack
  • Issues
  • Contact sales
Get involved
  • Roadmap
  • Contributors
  • Merch
  • PostHog FM
  • Marketplace

Docs

Getting started
  • PostHog Cloud
  • Self-hosted
  • Compare options
  • Tutorials
  • PostHog on GitHub
Install & integrate
  • Installation
  • Docs
  • API
  • Apps
User guides
  • Cohorts
  • Funnels
  • Sessions
  • Data
  • Events

Company

About
  • Our story
  • Team
  • Handbook
  • Investors
  • Careers
Resources
  • FAQ
  • Ask a question
  • Blog
  • Press
  • Merch
  • YouTube
© 2022 PostHog, Inc.
  • Code of conduct
  • Privacy
  • Terms