Team Fortress Wiki:Images
|“Gotta move that gear up!”
This team fortress wiki may contain content that is out of date.
You can help improve this team fortress wiki by updating the content as necessary. See the wiki style guide. The specific instructions are: Sometime before May 2011,
|This is an accepted guideline for images on Team Fortress Wiki. All images should follow these rules.
- Images used on the wiki should be uploaded directly to the site using the upload page. This avoids inline linking (also known as hotlinking) or external linking of images on external sites. This is to avoid a number of problems:
- Stealing bandwidth from other sources (leeching)
- Copyright ownership
- Ensuring the image links are more reliable as they are under our control
- The official Team Fortress Wiki is not an image hosting service, and any images uploaded to the wiki should solely be for use on this site, not your personal website or any other place.
- Each image on the wiki has a corresponding description page. On that page, you should document the copyright status of the image by selecting one of the pre-defined licenses. Unlicensed images will be subject to deletion. Please see the licensing help page for more information on the correct license to choose when uploading images.
- You should add the source and, if known, the author of an image in the summary section when uploading, or use the
- Fan art images should rarely be uploaded. In an exceptional case where fan art is relevant and notable, it should always be marked as non-official – especially when used in an article – and they should not take precedence over official artwork.
- Use descriptive titles. Suffix the filename with the content description. For example, acceptable filenames would be "File:2fort map.png" or "File:Unusual mullet green confetti.png". File names such as "File:lolhat.png" or "File:Myfavouriteloadout.png" are not descriptive, and will be subject to being renamed or deleted.
- Lowercase file extensions should be used for uniformity, i.e. .png rather than .PNG. This is also important as the software treats image names as case sensitive—this means "Filename.PNG" is considered a different file from "Filename.png".
- Avoid uploading images of the same subject under different names. It is better to overwrite an existing image with a better one than to upload it to a new name (unless the current name is not descriptive enough, or the file is using a different format). Images can be reverted back to previous versions if newer ones are deemed to not be improvements.
- Use of underscores in image names is unnecessary as spaces in file names will be replaced with underscores.
[[File:John Doe.png]]is the same as
- Images uploaded for use in userspaces should be prefixed with
NAMEis the user who uploaded that image, and will be using it on their own userspace.
Using categories for your images helps us sort them better, and makes it easier to find that particular image should it be relevant for an article in the future. Your image should always reside in at least one category; more if relevant. To place an image in a category, simply add
[[Category:CATEGORYNAME]], substituting CATEGORYNAME for the relevant category.
- Icons should be placed in one or more subcategories of Category:Icon images.
- Screenshots should be placed in one or more subcategories of Category:Screenshot images (this will be automatic if you use the
- Userspace images should be placed within the Category:User images category, by inserting
[[Category:User images]]into the image's summary field.
Additionally, a full list of all available categories can be found on the page Special:Categories. Should an appropriate category not exist, create a new one as necessary.
- png should be the primary file format for all images, unless otherwise noted. This includes, but is not limited to, icons, low-color illustrations (signs, icons, etc.), screenshots, in-game art, and similar images.
- jpg should only be used for photographs, when the source image is a jpg, or when cropping the png to make it fit the size limit is not an option.
- gif should only be used for animated graphics or when the original source is a gif image.
Design and Quality
- Larger images may be difficult for some users to view. Do not include extra information in your images, crop them to focus on their subject.
- Image size is capped at 2MB. If your image is larger than this limit then consider re-sizing or cropping your image, or saving it in a lossy file format.
- png can have their filesize reduced by lowering the number of unique colors in the image, due to the way png files are compressed. It is, however, not recommended to do so as it lowers the quality of images significantly.
- jpg files should always be uploaded at 100% quality to avoid as much artifacting as possible. That said, it usually shouldn't be necessary to refactor jpg images as they should only be used when the source is a jpeg, and thus require no editing.
- This site runs an automated crush bot which will losslessly optimize uploaded images. You usually don't need to do this yourself.
- Crop non-landscape images to show the important areas.
- Do not upload huge images—try to keep to a width of around 1280 (1280x1024 XSGA for 5:4 aspect ratio, 1280x960 for 4:3, or 1280x720 WXGA for 16:9).
- Do not blow up small images to larger sizes without good reason; this can detract from the overall quality.
- It is not recommended to resize images in an editing program, as MediaWiki can scale images automatically. Uploading a larger image that is cropped neatly means that higher amounts of detail can be seen if necessary.
- Images that require transparency should use the png file format. Gifs can also handle transparency, but only in a single indexed color as they only support 256 colors and do not have alpha channel support. This means they do not allow anti-aliasing of edges or blended color layers and shouldn't be used on the wiki for those reasons.
- Inline linking (also known as hotlinking) or external linking of images on external sites for display on Team Fortress Wiki should not be used. There are multiple reasons for this including bandwidth leeching, copyright, ownership, and availability issues.