bg3wiki:Image policy

Index • Guides • Modding • Discord

FAQ • Search • Templates (Documentation) • Community (Maintenance • Gags)

Editing policy • Verification • Content rules (Copyrights • Licensing)

Editing manual • Style manual • List of templates • Glossary

Style manual

Images

Spoilers

Content warnings

Images • Spoilers • Content warnings

File naming guidelines

These are general guidelines. Items and game mechanics follow separate guidelines, detailed later.

Use the following naming conventions andd file formats:

• Prefix_Page_Name_Suffix.fileformat.png/.webp

The Prefix should be a brief term that gives context to the image. When contextually applicable, it can be the category of the image. A suffix may be added when further clarification is needed. Both should be brief, concise and descriptive.

Examples:

• Underdark_Sussur_Tree.png
• Underdark_Mushrooms.png
• Underdark_Mush_Bibberbang.png
• Underdark_Arcane_Tower_NE.png
• Underdark_Arcane_Tower_S.png

Items and objects

Includes in-game items and objects.

• Faded images, 380x380
  • Prefix_Itemname_Faded.png/.webp
• Unfaded images, 144x144
  • Prefix_Itemname_Unfaded.png/.webp
• Unfaded images, 64x64
• Prefix_Itemname_Unfaded_Icon.png/.webp

The Prefix is usually the category of the item, and does not need to be included when it is unnecessary or the item or object lacks any specific category.

In cases where an item or object has multiple image variations, distinguish them by using a single letter following the item name:

• Backpack_A_Unfaded_Icon.png
• Backpack_B_Unfaded_Icon.png

When multiple items or objects share the same in-game image, only one file should be uploaded. Instead of uploading duplicate images, create Redirects to that image using the same naming conventions as above, corresponding to each item using that image.

Game mechanics

Includes spells, actions, abilities, conditions, passive features, and feats.

• Large faded images
  • Page_Name.webp
• Small unfaded icons
  • Transparent background
    • Page_Name_Icon.webp
  • Opaque background
    • Page_Name_Condition_Icon.webp

Image layout and presentation

Character images

For character pages, whenever possible, include both a cinematic portrait/screenshot and a transparent full-body model of the character. Display the cinematic portrait first and ensure the PageSeo template has been invoked with the cinematic portrait as the image parameter. This will help ensure consistency across character pages and external link previews (e.g. social media sites and Discord).

• 

  Cinematic Portrait Example - display this first.

• 

  Model Example

Exception: When an official render or character art is available - as in the case of Origin characters such as Lae'zel - display that image first.

• 

  Official Transparent Art - display this first.

Exception: For common, non-named creatures, it is okay to display a model first.

• 

  Transparent full-body model for the common, non-named Lesser Imp

Image alt text

When using the File template, alt text (text which appears when the image fails to load) should be added as necessary to improve accessibility. The text should be clear, concise and descriptive.

Alt text can be added to the File template with this parameter:

|alt=

Examples

Good alt text:

• {{File:A_Nice_Summer_Stay.png|alt=Astarion flinching in pain after being hurt by concentrated sunlight at the Githyanki Créche.}}
• {{File:Gale_Flirting.png|alt=Gale is serenading Tav while sitting on Mystra's picnic blanket at Lake Hurricane.}}

Poor alt text:

• {{File:A_Nice_Summer_Stay.png|alt=Astarion discovering the difference between a nice Summer stay and the full concentrated power of the sun.}}
• {{File:Gale_Flirting.png|alt=Gale sings while sitting at lake.}}