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.
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.
Entity graphics settings[edit source]
Use these graphics settings when taking NPC, scenery, detailed item, equipped item or override images. N/A indicates an irrelevant setting.
|Draw Distance||N/A||Shadow Quality||N/A|
|Anti-Aliasing Quality||Ultra||Water detail||N/A|
|Lighting Detail||Ultra||Ambient Occlusion||Off|
|Bloom||Off or On[notes 1]||Textures||Uncompressed|
|Anisotropic Filtering||N/A||Volumetric Lighting||N/A|
|Foreground FPS||N/A||Background FPS||N/A|
|Interface Scaling||N/A||Game Render Scaling||100% or 200%[notes 2]|
|Loading Screens||N/A||Ground Decoration||Off|
|Terrain Blending||On||Depth of Field||Off|
|Smooth Camera Fade||Off||Tree Canopy Fade||Off|
|Mouse-over Entity Highlights||N/A|
See Help:Editing/Taking images § Skybox and filters for a tutorial on setting up the appropriate skybox and filters.
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[edit source]
Images should be taken using the NXT client. Images that are taken in the Java client cannot be used to replace an image taken in the NXT client, regardless of any flaws in the NXT image. Permanent usage of Java images should be limited to cases in which an NXT version cannot be obtained (i.e. historical images). Temporary usage of Java images is permitted in cases where no NXT image exists, such as newly released updates. These should be tagged with until an NXT image is uploaded.
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 thetemplate.
Fan art[edit source]
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.
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.
Non-free images[edit source]
Non-free images include things such as official artwork, or images, icons or screenshots from the official RuneScape website or forums, may be uploaded but must come from official Jagex sources, such as official RuneScape social media outlets (such as Facebook or Jagex Moderator-run Twitter accounts) or the main website itself.
Third party images[edit source]
Images may be taken from the Jagex cache, game memory, Adventurer's Log, and/or extracted with any third party software should be tagged with . This template only applies to assets that are used in-game rather than images from a non-free source. Images taken in-game are preferred to those obtained using a third party.
The RuneApps model viewer may be used to obtain images. The settings that should be used are enabling hide floor and crop, and exporting in 4k quality should be used.
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!
MSAA or FXAA+MSAA anti-aliasing should be applied all images whenever possible, regardless of whether transparency is required or not. Current images without anti-aliasing or with FXAA anti-aliasing should be tagged with thetemplate, except for historical images.
Area or location images should use their natural lighting. Single subject images, such as those for NPCs or items, should use Midday lighting. Common sense should be used to handle exceptions on a case-by-case basis.
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.
To avoid redundancy, images of standard shop stock interfaces (e.g. File:Rasolo the Wandering Merchant stock.png) are not necessary as shop articles normally list their stock. Exceptions include shops that have unique interfaces, such as minigame reward shops (File:Stanley Limelight Traders stock.png).
Ground decoration[edit source]
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 and be enabled for environment scenes.
During the Evolution of Combat updates in 2012, the ability to sheathe/stow your avatar's weapons and shields when out of combat was introduced. To establish consistency, only unsheathed and relaxed stance equipped item images are to be used, and all equipment images are to be taken in Evolution of Combat mode, rather than Legacy.
Editors are to wear no equipment or cosmetic overrides when modelling 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.
During certain activities such as quests and combat, it is not always feasible to wear base clothing. As such, equipment may be worn during these times rather than using the "Hide-all" override. Equipment should be relevant, realistic, and accessible for the intended audience. Overrides, including familiars, should be turned off. Any visible pets or familiars should be necessary for the scene. Where it is realistically safe to do so, base clothing should be worn for quest and cutscene images.
Skin tone[edit source]
Natural skin tones (i.e. a skin tone that the Makeover Mage provides normally) are preferred over promotional skin tones. While not disallowed, promotional skin tones are considered cosmetic and images utilising them may be replaced by similar quality images of natural skin tones.
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.
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.
Equipment images should always be a full body image when possible, preferably using an Orb of oculus or freecam mode. 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. For melee armours with inferior and superior variants of items for each slot there should be two set images: a "heavy" set including the full helm, platebody, gauntlets, platelegs, and boots and a "light" set including the regular helm, chainbody, gauntlets, plateskirt, and boots. Shields, weapons and capes should be in a separate image with only that item equipped.
Detailed item images[edit source]
Detailed item images (DIIs) are images of the inventory model of an item, usually as it appears when dropped to the floor. This is typically achieved using freecam in areas of low ground detail, with transparency applied. The general settings specified above for anti-aliasing and so on still apply. There is no specification on the angle of a DII. DIIs should use Template:Detailed item license.
Items that can be dropped should always use the dropped model for the DII.
If an item cannot be dropped normally (has a 'destroy' or similar option), it may be possible to drop it with another method:
- Putting the item in a beast of burden and dismissing it
- Dying in an area that prevents gravestones (such as the Wilderness or the red Clan Wars portal)
- Putting the item in the Party Room chest and activating a balloon drop, then finding the item in the balloons
If the item cannot be dropped by any of these methods, a small DII can be obtained by using the item on Maemi, the cat in Draynor Manor, or Yaktwee Swinmari Cianta, south-west of the Tree Gnome Stronghold.
- Undroppable equipment
If Maemi is the only option for an item, and the item is equippable - particularly in the main- or off-hand slot - a cropped version of an equipped image can be used. The Revenant Walk animation allows a view of an entire main- or off-hand item without the player model's hands obsuring any parts.
The more different the equipped model is from the dropped model, the stronger the reason to not use the equipped model for the DII, even if the only alternative is Maemi. Particles and animations that appear when equipped but not in inventory, shape changes, stretching, and so on all contribute to this case-by-case decision.
- See Forum:Detailing the DII policy for the discussion adding this section.
Customisable items[edit source]
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[edit source]
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.
Map images should not be made. Instead the interactivetemplate should be used.
Glitch images[edit source]
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 recognisable.
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[edit source]
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 withor .
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 thetag.
A basic guide to adding transparency can be found at Help:Editing/Image transparency. File:Transparency - interface templates.png can be used to assist in applying transparency to interfaces that use that type of border.
Particle transparency and translucency[edit source]
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 thetag.
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. An advanced guide to adding translucency can be found at Help:Editing/Image translucency and one for transparency can be found at Help:Editing/Image transparency.
Inventory icons[edit source]
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
0x000001 (RGB 0,0,1). Take care that the 1px black border, however, is preserved; the border will be the hex colour
0x000002 (RGB 0,0,2).
Chatbox/player names[edit source]
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.
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[edit source]
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[edit source]
This section covers how images should be uploaded to and used on the Wiki.
Image name[edit source]
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.
- Images of item taken in the inventory should be called <Item name>.png, e.g. "Cake.png".
- Images of detailed items should be called <Item name> detail.png, e.g. "Cake detail.png".
- Images of Construction flatpacks should be called <Object name>.png, e.g. "Crude wooden chair (flatpack).png".
- Inventory images showing more than one of an item should be called <Item name> <Number of items>.png, e.g. "Acorn 5.png".
- Images of monsters, summoning familiars or NPCs should be called <Monster/Familiar/NPC name>.png, e.g. "Banker.png".
- Chatheads should be called <NPC/Item name> chathead.png, e.g. "Hans chathead.png".
- If chatheads have gender differences, the image should be called <Item name> chathead (<gender>).png, e.g. "File:Ariane's Hair chathead (male).png"
- Images of a player wielding an item should be called <Item name> equipped.png, e.g. "Rune scimitar equipped.png".
- If equipped items have gender differences, the image should be called <Item name> equipped (<gender>).png, e.g. "File:Juna's Gift equipped (female).png".
- Images of a player wielding a complete set of equipment with combat stats should be called <Type of armour set> armour equipped.png, e.g. "File:Bandos armour equipped.png".
- For sets of melee armour the inferior set of items should be called <Type of armour set> (light) armour equipped.png and the superior set of items should be called <Type of armour set> (heavy) armour equipped.png.
- Images of player wearing a complete set of equipment without combat stats should be called <Type of outfit> outfit equipped.png.
- If equipped item sets have gender differences, the image should be called <Type of armour set> armour/outfit equipped (<gender>).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)
- Images of pet icons should be called <Pet name>.png, e.g "Baby Troll.png".
- For pet versions of existing monsters or NPCs, or other pages that share the name, this should be called <Pet name> (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 name> pet.png, e.g "Eek pet.png".
- For pet versions of existing monsters or NPCs, or other pages that share the name, this should be called <Pet name> (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> (<colour>).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".
- Images of pet icons should be called <Pet name>.png, e.g "Baby Troll.png".
- 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 <description>.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".
- Images of quest rewards should be called <Quest name> reward.png, e.g. "Cook's Assistant reward.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 buffs and debuffs should generally be named <Buff/debuff name> (self status).png, e.g. "File:Flurry (self status).png" - if the name of the effect is very long it should be shortened sensibly, e.g. "File:Yakamaru tentacles (boss status).png" (the full name of the effect is Yakamaru can use his tentacles to choke the top DPS. You need to deal damage to the boss to free them!).
- Please do not upload images of inventory setups or action bars. For those, please use Template:Inventory and Template:Action bar, 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 (besides resolution), the full size image should be called <Subject> update image.jpg/png, e.g. "File:Serpentine super rares update image.png"
- Images showing the built appearance of Construction objects should be called <Object name>.png, e.g. "File:Oak larder.png".
- Animations should be called <Action>.mp4, e.g. "File:Heroic leap.mp4".
- Images of old versions of updated subjects should be called <Subject> old.png, with the <subject> 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[edit source]
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.)
Galleries can be added to pages with multiple images for display. The preferred usage is
<gallery mode="packed"></gallery>, though setting a mode is optional. The
packed-hover mode should be avoided because of its issues on mobile devices. See MediaWiki's image help for more information on the available modes.
Historical images[edit source]
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 tag. Instead, they should be tagged with the Historical image tag: .
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.
What to animate[edit source]
Animations are usually only necessary for:
- Magic spells
- Special attacks
- Enchanted bolt effects
- Unique and interesting item animations
- Unique and interesting NPC animations
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[edit source]
Due to the Legacy updates of 2014, Magic spells are graphically different between Evolution of Combat and 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.
It is preferred that animations do not have a solid colour as their background. These animations are allowed, but may be replaced by animations with a normal background as discussed during Forum:Greenscreen. The replacement should be of equal or better quality.
Animation length[edit source]
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.
File type[edit source]
Animations should be recorded in .mp4 format. 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[edit source]
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 files should be directly related to RuneScape and should be uploaded in the ogg vorbis file format. Full length music tracks and jingles are allowed.
Audio files from other sources should only be uploaded when absolutely required, and must follow the terms of the license of the source of the file.
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.
All image files, audio files, video files, or other media files of or containing RuneScape or any other Jagex intellectual property are property of Jagex and are used by the RuneScape Wiki with permission of Jagex. This includes edited files, files sourced from the game, and files extracted from elsewhere. Be aware that you may not have permission to use files from the wiki elsewhere - do so at your own risk.
Media files that are not of Jagex intellectual property should be marked with a license template to specify what license it is available under, and the original source (if the uploader didn't create it). Files available under 'freer' licenses (like a Creative Commons or other copyleft license) are preferred. Fair Use should only be invoked when absolutely necessary.