Branding

Guidelines for Facebook Applications on Non-Facebook platforms

Below are some guidelines that will help you accurately indicate that your application is compatible with Facebook, while helping you develop your own brand identity and avoid causing user confusion or damaging Facebook's brand assets. For complete information on Facebook's brand guidelines, please see our Brand Permissions Center.

---

Application Name

Off of Facebook, you may wish to accurately indicate that your application is compatible with Facebook. But you must not do so in a way that could suggest it is an official or endorsed Facebook application.

You may use the naming convention "[Your App Name] for Facebook" so long as (1) Your App Name is your own distinctive, original name, and (2) it is immediately clear that the application comes from you, the developer, and not Facebook, and that Facebook does not sponsor or endorse your application.

Examples:

Do:

• "Zwuitlite for Facebook" is OK because "Zwuitlite" is distinctive and original.
• "Bob's AwesomeApp for Facebook" is OK if your name is Bob, because the name informs buyers that you and not Facebook are offering this application.

Don’t:

• "Facebook Desktop" is not OK because "Desktop" is not distinctive and because Facebook cannot be the first word in your name.
• "Pages for Facebook," "Video+ for Facebook," "Photos for Facebook" are not OK because pages, video, and photos are all words that describe features of the application and features on Facebook.

Adding "plus," "+," "lite," "with push" or similar denominations does not make your name distinctive.

• "FaceMessages for Facebook" and "VideoBook for Facebook" are not OK because "Face" and "Book" are distinctive parts of the Facebook trademark.
• "FB Video" and "FVideo" are not OK because in these cases "F" and "FB" are clearly meant to refer to Facebook.

---

Icons

You should design your own application icon that represents your brand. Applications may not use or incorporate Facebook's F logo, or any modification or derivative of the F logo, in their application icon.

You may not use the FACEBOOK logo. You also may not use Facebook’s other graphics or icons, such as our well known silhouette logo.

Examples:

Do: The following examples use correct naming convention and do not use Facebook's logos or icons.

---

---

Don’t: The following examples make impermissible use of Facebook's logos and icons.

---

Open Graph Built-in Like Actions

You can use the Built-in Like action to create custom buttons in your app, but the button must not emulate or otherwise copy the design of Facebook’s Like buttons. For example, you may not use a “thumbs up” image with the word “like” in your Open Graph actions without prior written permission from Facebook, and any custom like button you create must not confuse users into thinking that your Open Graph action will result in a connection to a Facebook Page.

Examples:

Don’t: The following examples make use of Facebook's logos and icons.

Do: The following examples use generic graphics that do not use Facebook's logos and icons.