Skip to content

Faithful Branding Guidelines

A non-exhaustive handbook to use our branding effectively.

Faithful is a community project that's not meant to be taken too seriously. Our branding, however, was made with certain goals in mind – so if you're into this sort of thing and want to represent Faithful properly, we'll be extra grateful if you follow these guidelines.

Do remember that our license still applies when using our branding. This means that you cannot use our branding with the intent to confuse users into believing an unofficial project is official.

Finally, you can find all our branding assets on our GitHub repository.

Part 1: Language

Faithful is the product of the community. If a community you rely on cannot understand you, that's a problem.

This concept basically boils down to not using unnecessarily formal language. Certain settings may require more or less formal language than others (e.g. licenses and guides should be more professional than regular posts), but if the average person doesn't understand what you're talking about, you either need to add in some definitions or simplify your language a bit.


Classic Faithful 32x goes all out on nostalgia!


Classic Faithful, formerly named the Emulated Vattic Textures or "EM" project, attempts to answer the question "what if Vattic had never left Faithful".

To refer to the project as a whole, "Faithful Resource Pack" or "Faithful Project" is preferred when Faithful hasn't been already introduced. Once the Faithful name has been established, you can simply use "Faithful" from then on.

For specific projects, use (division) Faithful (resolution)x (style) as the format for each specifier.


  • Faithful Project
  • Faithful 32x
  • Classic Faithful 32x
  • Faithful


  • Faithful x32
  • Faithful Classic
  • Faithful32x32
  • faithfull

Part 2: Logos

View all our logos here

Logos work well for displaying our branding in places with limited space. This includes, but is not limited to cards, thumbnails, and buttons. Don't use our logos as a substitute for showing the name "Faithful" itself, but use them when the name is already established instead.

For most general-purpose applications, use our plain logo. This logo additionally encompasses Classic Faithful, but if you specifically want to refer to Classic Faithful, you can use its respective plain logo as well.

Left: Plain logo. Right: Classic Faithful plain logo.

If you only want to refer to one project, such as in a card, use that project's respective logo. The Classic Faithful logos have different margins to the regular Faithful logo, so bear that in mind when adjusting sizes.

You can use a monochrome version of our logo in small spaces if using the regular logo would look visually noisy or be hard to read.

All our logos should always retain their pixel art form. Even when using the monochrome logo, don't simplify the shape into vectors.

Left: Correct depiction of the Faithful monochrome logo. Right: Incorrect depiction.

Finally, our logos should always be centered based on their main hexagonal part. The numbers and symbols in the bottom-right corner should not be taken into account when positioning.

Left: Correctly centered Faithful 32x logo. Right: An example of incorrect centering; Note that the logo on the right has been centered based on the whole image, and not just the hexagonal part.

Part 3: Logotexts

View all our logotexts here

Logotexts were designed for users to be able to use a logo and a wordmark at the same time without having a clash in resolution. Each logo has a corresponding logotext and this can be used if the Faithful name is not already well established.

The Faithful logotext.

Always make sure to put logotexts on plain or low-contrast backgrounds — readability can be negatively impacted with noisy backgrounds. Please also note that the text and the logo that make up the logotexts are inseparable, so don't use the pixel art text by itself.

Top: Correct placement of a logotext that ensures it's easily readable. Bottom: Poorly placed logotext.

Part 4: Wordmarks

View all our wordmarks here

Wordmarks tend to be pretty big and bold, so use them sparingly for large banners and other big areas. They're usually the preferred branding when placed over busy backgrounds such as screenshots.

The Faithful banner.

The plain Faithful wordmark is preferred for most purposes, but specific projects also have their own wordmarks, similarly to the project logos.

In addition, both cracked, flat, and outlined versions exist. As a rule of thumb, use the flat versions for referring to Faithful (or Classic Faithful) as a whole, the cracked versions for specific projects, and the outlined versions to help readability when necessary.

Each Faithful wordmark variation.

Wordmarks don't tend to scale well, so refrain from using them in small spaces — consider using the logo or simply typing out the name when space is limited.

An example of a wordmark not scaling well.

However, don't mix logos and wordmarks, since that's what the logotexts are for. The reasoning is because the pixelated logos don't mix well with the high-resolution wordmarks.

A logo next to a wordmark. A logotext is much better suited for this situation.

Part 5: Typography

Download the Faithful fonts here

The Faithful font should be used for titles and headings, while any neutral sans-serif is preferred for body text. This is primarily because the individual pixels in the Faithful font blur together, hindering legibility at small scales.

The individual pixels on a logotext also tend to blend at small resolutions so you're usually better off just typing the name out in a regular font.

Left: Good diversity in font sizing. Right: Blends together from the uniform size and font.

The semibold Faithful font should be used for large headings and the regular Faithful font for sub-headings. Only use the bold Faithful font for top-level titles when more than two levels of nested titles are required, due to its low readability and large horizontal footprint.

Each font weight and where it should be used.

Part 6: Scaling

In general, the hierarchy of branding elements to be used should be as following (from largest to smallest space available):

Wordmark → Logotext → Logo → Text

Always leave padding around the edges of any logo, logotext, and wordmark. Specific ratios don't really matter as long as the padding is even on all sides and the respective branding doesn't appear too large.

Left: Correct padding and scaling of the logo. Right: Incorrect padding and sizing.

Don't distort our branding to fit in a given space. Instead try using another suitable image or simply typing out the Faithful name using the format specified in part 1.

Do not.

Part 7: Colors and Backgrounds

Faithful has a fairly limited color palette used throughout most of the branding, and a set of background images to complement them.

The main brand color is used for most accent colors, such as buttons or embeds. It works in combination with the "generic" background image.

The main Faithful brand color and image.

Each pack additionally has a unique color and background screenshot assigned to it.

All Faithful project colors with their respective images.

A background image works well with a wordmark, decently with a logo, and not very well with a logotext. This placement hierarchy should be used to determine an element to go on top of a background image. If you absolutely have to use a logo or a logotext on a background image, it is recommended to add a drop shadow and/or blur the background.


These guidelines probably look very different to your standard 50-page corporate brand guidelines with every single use case laid out, and that's because at the end of the day, as long as you're getting your point across and aren't confusing anyone, it's probably fine. We aren't fussed if your padding is a few pixels off, or if you're using the wrong font size — just don't be horribly inconsistent with everything else and that's about it.

As with all our docs, if you have any suggestions leave them on our Discord server. Good luck with whatever you're doing!

Credits go to…

  • Evorp (content, some images)
  • Pomi108 (images and some content ideas and edits)
  • Klonoa (an image)

This website was made using the VitePress framework. View the source here!