RuneScape:Images and media policy

The images and media policy describes preferred image source, content, and usage in articles and other pages. It applies to all images equally, regardless of uploader, format, and subject.

Summary
All images must be suitable for use on a mainspace page; if they are for your userpage, please upload to a site such as imgur instead. If you are uploading a replacement for an existing file, please go to that file's page and use the "Upload a new version of this image" link to upload your image. Ideally all images should be taken with 4x anti-aliasing active, be in the .png file format, and should have a good name. Images of equipped items should only have the item that the image is about being worn.

=Images=

Source
Nearly all images uploaded to the Wiki should be taken by the uploader themselves in the RuneScape game client (in layman's terms, while playing RuneScape). A screenshot is taken by pressing Shift + Prnt Scrn, Prnt Scrn, or Command + Shift + 3 for Macs while the RuneScape window is open, then pasting it into an image editor, usually by pressing Ctrl + V (Command + V for Macs) or opening the Edit menu and selecting Paste. Once in the editor an image can be cropped, edited, and saved (preferably as a .png, details below). Other possible sources, and our related policies, are:

Java and NXT
Images may be taken from both the Java or NXT version of the game. However, NXT is the preferred client for all images, especially ones that require a large draw distance. Images that are taken in the Java-based client should be replaced with ones from NXT whenever possible.

Bestiary
RuneScape Bestiary images will be allowed for use in articles only if a better image cannot be captured in-game. Bestiary images should be marked with the Bestiary image template.

Game Guide
Game Guide images can be used, but only if editors cannot take a superior screenshot on their own. Furthermore, Game Guide images must be marked with the Game Guide image template.

Fan art
Fan art that has been displayed on the RuneScape website should not be uploaded. Other types of fan art such as personal fan art and fan art created by another author is also not acceptable on the wiki and is subject to deletion. Fan art does not include RuneScape images that have had transparency or acceptable particle transparency added, slight colour enhancements or added brightness.

Fansites
Images from other fansites cannot be uploaded. Most websites ask that the images featured there not be used elsewhere, and it is the wiki's policy to honour that request.

Cache
Per RuneScape:Jagex cache, images from the cache are forbidden. This includes, but is not limited to, images from private servers and hex editors.

Content
This section covers guidelines which are applied while in the game. These deal with manipulating the game environment to produce the highest quality images. If these conditions cannot be met, an image can still be uploaded. A Standard detail image is better than no image at all!

High detail
All images should be taken in HD graphics. Existing images which are not in HD graphics mode should be tagged with the sd template unless they are historical images.

Anti-aliasing
4x anti-aliasing should be applied all images whenever possible, regardless of whether transparency is required or not. Current images without anti-aliasing should be tagged with the No AA template, except for historical images.

Lighting detail
High detail lighting adds shading and realistic reflections to objects in the environment. While attractive for environment scenes, it can be distracting and obscure details in monster, NPC, and other single-subject images. For these reasons, it may be a better to set it for low when taking screenshots of these subjects.

Interface
When taking screenshots of the interface (for example, images of the settings menu or cutscenes that show the chatbox), the New Interface System released with RuneScape 3 must be used. The only instances in which the Legacy interface is allowed are when the topic pertains exclusively to Legacy Mode.

Ground decoration
Ground decoration shows or hides ground accents such as pebbles or grass. These ground decorations often show above or cover up parts of the subject of the screenshot. As such it should be turned off for single-subject screenshots. It can be left on for environment scenes.

Fog
Fog should always be turned off except for scenic images. Doing so will ensure that area fog does not manipulate the color of items like detailed item images and worn item images.

Stance
During the Evolution of Combat updates added to the game in 2012, the ability to sheathe/stow your avatar's weapons and shields when out of combat was introduced. To achieve the highest quality standard of images, only unsheathed and relaxed stance equipped item images are to be used.

Due the Legacy updates of 2014, stances are now different when using Evolution of Combat or Legacy. For consistency purposes, in addition to using only unsheathed and relaxed stances, all equipment images are to be taken in Evolution of Combat mode rather than Legacy mode.

Costumes
Editors are to wear no equipment or cosmetic overrides when modeling for an image. Wearing other equipment that is irrelevant to the subject item may distract the purpose of the image. If an image is found to have distracting equipment or overrides, the image should be tagged for retaking. Benign and undistracting costume parts (such as plain boots) can be ignored.

Gender
Any gender may be used for any image (providing the subject matter is available to both genders), and users should not replace images solely to depict their gender of choice. Replacing a low quality image with a higher quality image is perfectly fine, regardless of gender. Both genders may be depicted on equipment articles if there are equipment variations.

Cutscenes
For cutscenes, only the most important parts should be displayed on the respective article. There should generally be no more than 4 images per cutscene. Action shots of cutscenes may look good, but they also increase the pageload a lot without adding anything useful to guides.

If there are plenty of images available that show cutscenes, they can be added to a separate page, pagename/cutscene. That page can then be linked to on the main page for that quest, thus allowing viewers who want to see more to see more.

Water images
DirectX is the preferred graphics mode for water images, but common sense should be used to determine if an image would be better taken in OpenGL.

Equipment
Equipment images should always be a full body image when possible, preferably using an Orb of oculus. An image of the full body is preferred over just the head, feet, weapon or any other separated part. The equipment image is meant to show the body of a player wearing the item. To show the item in detail, detailed item images can be made.

For items in a set, it is preferred that the whole set should be taken as part of the picture, while the weapons and shield should be separate.

Customisable items
Images of items and equipment with a great number customisable cosmetic properties should only display the item in its default state. Having multiple images of the same item increases the page load and inflates the amount of work when maintaining, managing, and updating the images. Taking a picture of the customisation interface is a superior option.

Setup images
Images of equipment setups for strategy guides should not be uploaded due to the high maintenance required and the multiple options for personal setups. Tables should be used on the strategy guide instead of a setup image.

Chatboxes
Images focusing on text within the chatbox (an NPC speaking, a warning, etc.) should not be uploaded. Instead, translate the chatbox's message into the content of the article.

Minimaps
Minimaps should be a maximum of 250x250 px, at 100% zoom, with a maximum dimension of 75x75 for the blue marker. Icons should be taken from the minimap instead rather than the world map.

Glitch images
A glitch image (file, media, etc) may be uploaded if it meets the following requirements:
 * The image is of original content and does not contain material that may be deemed of duplicate nature to any other media hosted on the wiki.
 * The image augments text describing such glitches in such a way that simply describing the glitch in a purely textual format would not or could not define the contents of the glitch adequately.
 * The image portrays the glitch in a manner such that the contents of the glitch are readily notifiable and/or recognizable.

Format
This section covers preferred standards which are set or applied after the screenshot is taken, outside of the RuneScape client. This is usually in an image editor.

File type
The preferred image format is .png (in lowercase letters) because it has no compression artefacts and it supports transparency. Images can be saved in .png by changing "Save as type"(or similar) option at the bottom of the save window in most image editors. Images not in .png format should be tagged with jpeg or gif.

Transparency
All images showing items, objects, scenery or NPCs should have transparency. This means that the image's background should be deleted and replaced with transparent pixels. If the image editor cannot do this, editors are free to upload images without transparency to which other editors can apply transparency, or they can paint over the background with another colour (preferably white) to make adding transparency much easier and faster for other editors. Existing images without transparency should be tagged with the trans tag.

Particle transparency and translucency
Images that have particles or bloom effects may have their particles recreated to support transparency, as long as the recreated particles are not different than the original particles at a glance. Recreated particles must look like the original as much as possible. Images that require translucency may also be recreated as long as the newly created image represents the original image in an accurate way. Existing images without particle transparency or translucency should be tagged with the Translucency tag.

If adding particle transparency or translucency is deemed too arduous, normal transparency may be added without cutting out particles, but the image should then be reverted to the original state without transparency if it is aesthetically superior over a partially transparent form. Particle transparency or translucency can be applied later.

Inventory icons
Inventory images must not contain shadows. The shadow should be deleted and replaced with transparent pixels. Inventory icons that still have their shadows should be tagged with the Inventory shadow template.

Chatbox/player names
The chatbox must be cropped away if it is not relevant to the image. If it must stay, Jagex Moderator names can appear as they may be relevant; however, player names are almost never relevant and should be removed in a way that does not distract from the image or replaced with a player spoof name.

Cropping
Be sure to crop the image to show only what is needed to serve the image's purpose. Crop away any irrelevant pixels that would distract from the image's original purpose. For example, a player wishing to create an image showing the bankers at the Grand Exchange should keep only the pixels showing the banker and possibly the desk they're standing at. The rest of the building and players should be cropped away as much as possible.

Image size
The maximum allowed file size for images uploaded to the wiki is 10 megabytes (10MB, 10240KB). Images which exceed this size are usually unnecessarily large and should be scaled down or cropped to a more reasonable size.

Image use
This section covers how images should be uploaded to and used on the Wiki.

Image name
When uploading an image to the Wiki, the name should be as descriptive as possible. It is helpful to identify how the subject is being depicted, whether it is a detail image, an inventory icon, an equipped image, and so on. Names such as "Screenshot-01" or "Untitled 1" are not acceptable. Likewise, including player names in the image title is not allowed. As for the extension, .png is preferred over .PNG.


 * Items
 * Images of item taken in the inventory should be called .png, e.g. "Cake.png".
 * Images of detailed items should be called  detail.png, e.g. "Cake detail.png".
 * Images of Construction flatpacks should be called .png, e.g. "File:Crude wooden chair (flatpack).png".
 * Inventory images showing more than one of an item should be called  .png, e.g. "Acorn 5.png".
 * Characters/players
 * Images of monsters, summoning familiars or NPCs should be called .png, e.g. "Banker.png".
 * Chatheads should be called  chathead.png, e.g. "Banker chathead.png".
 * If chatheads have gender differences, the image should be called  chathead .png, e.g. "File:Ariane's Hair chathead (male).png"
 * Images of a player wielding an item should be called  equipped.png, e.g. "Rune scimitar equipped.png".
 * If equipped items have gender differences, the image should be called  equipped .png, e.g. "File:Juna's Gift equipped (female).png".
 * Images of a player wielding a complete set of armour should be called  equipped.png, e.g. "Rune armour set (lg) equipped.png".
 * If equipped item sets have gender differences, the image should be called  equipped .png, e.g. "File:Tribal outfit equipped (female).png".
 * Images of individual overrides and override sets should follow the above two points, using in-game names (found in the Wardrobe or other relevant interface)
 * Pets
 * Images of pet icons should be called .png, e.g "Baby Troll.png".
 * For pet versions of existing monsters or NPCs this should be called  (pet) icon.png, e.g "Jadinko (pet) icon.png".
 * In cases where the pet's icon in-game name differs from the pet's name, the icon name takes precedent.
 * Images of the pet itself should be called  pet.png, e.g "Eek pet.png".
 * For pet versions of existing monsters or NPCs this should be called  (pet).png, e.g "Pig (pet).png".
 * Images of pet chatheads should be called <Pet name> chathead.png, e.g. "Mackers chathead.png".
 * Images of pets with multiple colours should be called <Pet name> .png, e.g. "Pet cat (black).png".
 * Images of pets with multiple growth stages should be named in relation to the breed and current stage, e.g. "Baby chameleon.png".
 * Places
 * Images of sceneries or locations should be called <Name of scenery/location>.png, e.g. "Lumbridge Castle.png".
 * Images showing the location of something, that are not just images of the world map should be called <Object> location.png, e.g. "Dragon Slayer mine map location.png".
 * Images showing the location of a Treasure Trail should be called <Type> clue .png, e.g. "Emote clue Wave Lumberyard.png", "Coordinate clue 09.33N 02.15E.png", "Cryptic clue Port Sarim Captain Tobias.png", "Scan clue Haunted Woods south-east of Canifis bank.png".
 * Interfaces/icons
 * Images of quest rewards should be called <Quest name> reward.png, e.g. "Cook's Assistant reward.png.
 * Images showing the location of something on the world map should be called <Object> map location.png, e.g. "King Roald location.png".
 * Images of skill-specific icons should be called <Object name> icon.png, e.g. "Yew tree (Construction) icon.png". This includes Construction icons and Hunter icons.
 * Images of Solomon's General Store icons should use <Item name> icon.png, using in-game names (found in the Wardobe or other relevant interface) and appending (male)/(female) if needed, e.g. "Deathless Regent outfit icon.png" and "Blessed Sentinel outfit icon (female).png".
 * Images of Construction icons should be called <Object name> icon.png, e.g. "File:Crude wooden chair icon.png".
 * Please do not upload images of inventory setups or action bars. For those, please use Template:Inventory and Template:Actionbar, respectively. See the template page for information on how to use those templates.
 * Updates and banners
 * Images of a head banner from the main RuneScape site should be called <Banner subject> head banner.jpg, e.g. "File:Runescape through the Ages head banner.jpg"
 * Images of a banner from the RuneScape game lobby should be called <Banner subject> lobby banner.png, e.g. "File:Fate of the Gods lobby banner.png"
 * Images used as a header banner in an update post should be called <Update subject> update post header.jpg, e.g. "File:Heist update post header.jpg"
 * The thumbnail version of images used in update posts should be called <Subject> update image thumb.png, e.g. "File:BTS July 2012 Philipe thumb.png"
 * The full version of images used in update posts should be called <Subject> update image full.jpg, e.g. "File:BTS July 2012 Philipe full.jpg"
 * Where there is only one image used with no difference between thumbnail and full size, the image should be called <Subject> update image.jpg/png, e.g. "File:Serpentine super rares update image.png"
 * Other
 * Images showing the built appearance of Construction objects should be called <Object name> built.png, e.g. "File:Oak larder built.png".
 * Animations should be called <Action>.gif, e.g. "File:Pulling Christmas cracker.gif".
 * Images of old versions of updated subjects should be called <Subject> old.png, with the following all of the above rules, and added to graphical updates, e.g. "File:Lesser demon old.png".
 * Images of concept art should be called <Subject> concept art.jpg/png, e.g. "File:Slayer master cape concept art.png"

If the image is of an item, monster, npc, or quest reward, please try to keep the name consistent with the name of the article for that thing. For example, Bob (smith).png instead of Bob.png. Also keep things such as capitalisation and punctuation consistent not only with the article name, but with the guidelines above. Spaces should always be used in file names instead of hyphens, etc.

An effort should be made by users uploading files to this wiki to see if in fact the item or image has already been uploaded previously, and to preserve existing naming conventions for this item or for similar kinds of images. Attempts to upload a new image under a new file name for something that already exists on this wiki may result in that image being deleted.

Use in articles
All images hosted on the wiki must be used in the main article namespace at least once. Project-related images, such as the sysop crown, are an exception. Since the Wiki is not an image host, no personal-use images are allowed to be uploaded, whether it be for use on a talk page or a signature. You cannot justify a personal image by adding it to the pages of items that appear in your image! If you want a personal image to appear on the wiki, you must use either ImageShack, imgur, or Photobucket, since they are currently the only such websites supported by the wiki. (Hosting sites such as Tinypic aren't supported and so will only display an html link.)

Historical images
Images taken in RuneScape Classic or before a significant appearance update should be kept. New screenshots will replace the old at the top of the page and other places of prominence. The old images should be kept, but moved to the Graphical improvements page. Historical images are allowed to be in Standard Detail since the image cannot ever be recaptured in HD; as such they should not be marked with the Sd tag. Instead, they should be tagged with the Historical image tag: reason for being historical.

Templates
There are several templates designed for use on file pages. These can mostly be split into two categories; licenses and maintenance. These templates should be included on the image page. They should link, if possible, to the article of the subject which it depicts.

Others
=Animations=

What to animate
Animations are usually only necessary for:
 * Emotes
 * Magic spells
 * Special attacks
 * Enchanted bolt effects
 * Unique and interesting item animations
 * Unique and interesting NPC animations

Combat
If the animation requires the player to be in combat, use a player or a monster with a low amount of life points. If using a player, make sure they have Auto retaliate set to Off, and if using a monster, ensure it is killed in one hit so its retaliation does not interfere with the animation.

Magic spells
Due to the Legacy updates of 2014, Magic spells are graphically different between Evolution of Combat Legacy modes. Both versions should be uploaded separately and should not replace one another, using the relevant combat mode name in parenthesis in the file name.

Animation length
Make sure that the animation is long enough. They must be long enough to capture the entirety of the subject. Also include about a second of buffer at the end before the animation loops to prevent hectic looking animations. Likewise, ensure that the animation only records what is necessary. Be sure to trim excess footage from the beginning and end.

Animated PNG
Animated .png (.apng) files should not be used. They are currently supported by few browsers, so due to browser compatibility concerns, do not use any.

File size
Animations must have a filesize less than 7 megabytes (7000kb). When animations are larger than this, they may be longer, show more than what is necessary, or their dimensions may be too large. Some frames should be removed or the image itself retaken or cropped.

=Audio= Complete audio files may not be uploaded. Uploading complete files or even linking to those files other than in links to websites that have a legal and bona fide copyright permission from the original copyright holder is illegal. Even for encyclopaedic purposes or for purposes of critical commentary, there are very narrow and defined limits for how much or even if the audio files can be used. Musical files, jingles, and sound bites must not exceed 30 seconds in length, must be directly related to RuneScape, and must be uploaded under the "ogg" file extension.

Policy on this particular point is not a settled issue on this wiki, and this should be used as a guideline only. Keep in mind that all items uploaded to this wiki must be either released under the terms of the CC-BY-SA copyright license or compatible with that license. See RuneScape:Copyrights for more information.

=Video= Streaming videos (such as YouTube) should not be embedded in articles. If a video adds significantly to an article, link to it instead of embedding it, however there must be consensus to do so. Videos are permitted in update news posts, such as Update:Order of Ascension, as news posts are to be copied verbatim. Since embedded video is not actually hosted at the Wiki, they are allowed without limitation in the user namespace.

Any disputes about any media meeting the criteria above should be discussed on its talk page and tagged with the relevant templates.