Co-branding logo guidelines
Innovation happens when collaborators come together for a common purpose. This is true in open source communities and it’s true for our customers and partners. When we show up with our partners and customers, our goal is to show two brands in an equal partnership that acknowledges the value both bring to the table. We do that through co-branding.
Which logo comes first in the co-brand depends on who is leading the marketing effort. When Red Hat is in the lead, the co-brand should follow our co-brand logo template with Red Hat first. If the partner is in the lead, the co-brand should follow the partner’s standards for co-branding logos.
Red Hat-led co-branding
A good relationship with our partners and customers is built on mutual respect. We should always treat their brand with the same respect we give our own. Before moving forward with a Red Hat®-led co-brand, answer these questions:
Is Red Hat the lead brand?
If Red Hat is the lead brand, use our co-brand guidelines and templates. If the partner or customer is the lead, they should follow their own brand guidelines and templates. Review the partner-led portion of this page for more information.
Are we co-branding with a peer brand?
Co-brand lockups should always use the Red Hat logo and the logo for the parent brand of the customer or partner. We never create a co-brand lockup with a product, program, or event logo.
Do we have permission?
We need the customer’s or partner’s permission before we use their logo, even if we’ve used it before.
Does the partner or customer have co-branding guidelines?
If so, make sure we know what they are and follow them, like we’d expect them to do for us.
Lockup options
Logos come in all shapes and sizes, and partners and customers may have rules or expectations for how we use their logo. To accommodate that, we have three lockup template options. All three will work for some partnerships, while others might have only one that works. No matter which template we use, the co-brand should feel balanced. The logos should be as close to the same visual size and weight as possible.
All co-brands should be used with appropriate clear space. Clear space is the space around the co-brand that should be free of other logos or distracting graphics. Minimum clear space for co-brands is the height of the “R” in the Red Hat logo. More is better.
Wide logos
A horizontal lockup works best when the partner’s logo is wide.
Tall logos
A stacked lockup works best when the partner’s logo is narrow.
Narrow space
A vertical lockup works best when you’re placing the co-brand in a square or narrow space.
Using 3 or more logos
When talking about a collaboration with more than one partner or customer, think carefully about the relationship between the brands. Make sure we’re representing them accurately and respectfully.
Tri-brand
When the relationship between three brands is equal—like when telling a joint customer and partner story—use a tri-brand.
Co-brand plus another partner
When the relationship between two of the brands shown is stronger—like if a jointly developed product is being sold by a reseller—add the third partner’s logo in a separate area.
Logo wall
When we want to show more than three logos at once—like for a list of sponsors or participants—use all of the logos independently but with equal weight.
Things to avoid
Not this: Do not co-brand a Red Hat product, team, initiative, or event logo with a partner or customer.
Not this: Don’t co-brand with a product, division, or event of a partner or customer.
Not this: Don’t use a different template or dividing element when Red Hat is the lead brand.
Not this: Don’t use a format that makes the logos appear unequal in size/weight.
Not this: Don’t co-brand icons alone.
Not this: Don’t generate co-branded logos using AI.
