BugSplat Brand Guidelines

Is your team getting ready to ship your software with BugSplat crash reporting baked in? Want to announce it to customers or other stakeholders?

That's great! We just have a few small guidelines that we ask you to follow.

These guidelines were inspired by Bootstrap's Brand Assets which follow a similar post by MailChimp.

Download all assets

Below are the acceptable iterations of our logo for light and dark backgrounds.

BugSplat
BugSplat
BugSplat

The BugSplat Bug

We love our Bug. It's been seen millions of times around the planet in connection with our brand, but not everyone will be familiar with it. If you are using our brand in a setting where the audience may not be familiar with BugSplat, please use our full logo.

BugSplat
BugSplat
(correct)
BugSplat
(incorrect)
BugSplat
(incorrect)

In Writing

Our company and crash reporting tool should always be referred to as BugSplat. Specifically note the CamelCase (BugSplat) and that it is always written as one word.

BugSplat

(correct)

Bugsplat

(incorrect)

Bug Splat

(incorrect)

Colors

Since the beginning BugSplat has always been a colorful brand. Today we use these colors primarily in out logo, in our docs, and on our site.