Fallout Wiki
Fallout Wiki


Images are subject to the general content criteria. In addition, there are some specific rules for this type of content outlined below.


Article images

  • Images should be of good quality.
  • Images should never include parts of the UI (HUD, crosshair) unless the point of the given image is to illustrate the UI itself.
  • Images should have a descriptive name, e.g. following the format [Game abbreviation][Content of image][Detail] such as FO76 Foundation signage.png.
  • Fallout 76 images should be taken in a professional pose (idle), not when emoting.
  • Files should be uploaded in the highest possible resolution.


  • The order of images are organized by type as in-game, additional maps, Nifskope renders/texture files, concept art, cut or promotional, and other.
  • For Fallout 76, the gallery for locations articles are organized to group changes by update with the newest on the top. Wiki markup with the name of the update is used instead of subheaders.

Recreated assets

A recreated asset is a image file that is based on an asset that appears in game, but has been edited by the uploader in a substantive way. For example, cropping a screenshot to remove the player HUD is not a substantial enough edit to make the file a recreated asset, but filling in holes that are present on an in game flag is substantial enough to make the resulting file a recreated asset. Data mined textures are not recreated assets, as they are created by the developers but may not have visual effects that are applied to the in game version. Deceased non-player characters resurrected with console commands are recreated assets for the purpose of this policy.

When deciding on what type of asset or image to use, the main considerations are the images quality, the isolation of its subject, and the faithfulness to the subjects in game appearance. Above all, the main aim should be to provide an accurate representation of a players experience with the subject while playing the game. What asset type is used should be whichever most accurately conveys this player experience. For example, screenshots are best used to show NPCs, armor, clothing, and locations as they appear in game but textures are better for weapons, consumables, ammunition, and world objects.

File pages for recreated assets must follow these guidelines:

  • The file name must identify it as a recreation. For standardisation "recreated" must be used, not euphemisms such as "clean" or "restored" as these can give an inaccurate impression of the file's origins.
  • The file description must state what in game asset it is replicating, what game this asset is originally from, what changes have been made compared to the in game asset or a link to a file page of the in game asset, and depending on the rarity of the asset where in this game it can be found (for example, if the original asset is only found in a single specific location that location should be listed, but if it is found easily in the game world it does not need to be specifically mentioned).
  • It is on the uploader to provide proof of the images origin if it is called into question, and if they cannot provide this information the image will be deleted.
    • Image files predating the creation of this policy in 2022, whose uploaders are no longer active in the wiki community, are exempt from this specific guideline. If an image of this nature is called into question, it is on the user who has raised the issue of the files origin to make all reasonable efforts to find the files in game.

Music players

Music players placed on articles and user talk pages (YouTube player, etc.) should not be set to automatic play upon page load. Autoplay is unregulated on your user page.

See also

Policy vote forum overview
PolicyImage policy
Amendment 1Userpage images · Vote · 16 August 2010 · 10-2-1
Amendment 2Gallery image order · Discussion · Vote · 2 February 2022 · 12-0-1
Amendment 3Allowing recreated assets · Discussion · Vote · 1 June 2022 · Ratified 8-2-3
Amendment 4Recreated assets guidelines/Lazarus images · Discussion · Vote · 10 June 2022 · Ratified 9-0-1; 10-0-1
Related topicsContent Policy · Content organization guideline · Article layout guideline