The following are some guidelines concerning the naming, categorization, and usage of images on the Night of the Dead Wikia.

Fan WorkEdit

Fan works is not suitable for general use on the wiki. They may still be uploaded but their numbers should be limited and their use confined to small roles.

Other Things to ConsiderEdit

  • Do not upload duplicate images. A duplicate is any lower quality version of an existing image. Replacing an image with a higher quality version is permitted, given the new version is appropriately sized.
  • New images should depict something that no existing image does, perhaps in terms of the act depicted or point of view.
  • Check the image categories and unused file list to see if an appropriate image has already been uploaded.

Where to UploadEdit

Many images exist within the wiki and even more are available. When uploading images to an article, the question must be asked as to where they should be inserted. This is subjective, and editing should be in good faith, but a few pointers should be remembered:

Image PlacingEdit

Images are there to supplement the text, not overshadow it. In other words, images should not disrupt the flow of the main text by stacking. It is always best to preview an image edit before saving changes for this reason. Any supplementry images can be worked into a gallery. Generally, images should not be parallel to each other, on either side of the text. See how large an image is, where it goes down to vertically, and once its reached its lowermost point, the section below can be supplemented by another image.


"Game images go with game sections, lore images go with lore." This is only really applicable where articles are divided as such, but for the most part, game sprites should be reserved for the gameplay section of an article, whilst artwork, cinematics, etc. should be reserved for the in-universe content. There are exceptions to this-portrait images have become more detailed and can be fitted into an in-universe section if appropriate. Also, some gameplay templates begin in the top section of an article. Artwork/cinematics should be used here, as it's the core image of an article.

Which Image?Edit

Are some images better than others? Such a question is subjective and there is no right answer. Generally, the more detailed the image, the 'better' it is, and should be used over more simplistic ones (e.g. game sprites, which are best reserved for a gameplay section as stated above). The highest quality images generally fall into the range of (concept) art and cutscene screenshots. Keep in mind however, that while cinematic/cutscene scenes may have more detail, they are limited in use to the moment they are referring to. Art is more general however, and can therefore be inserted in more places within an article where appropriate.

When art and screenshots depict the same event, there is no real "correct" answer as to which should be inserted. Keep in mind the quality (which might lend itself to screenshots) but also that screenshots have been extracted by users, while artwork is from official sources and therefore more appropriate in some cases.


Articles marked for deletion are covered further down, but the topic is covered here to an extent. As what is hopefully clear by now, there are often more images than an article can easily fit and some may depict similar events/individuals. Does this mean that these images should be deleted? In a word, no. Firstly, image galleries exist to catalog images and are far from overflowing. Secondly, an image that is similar to a 'better' one may still have a use of its own, such as the pros and cons of artwork and screenshots. Thirdly, there is the reason of posterity. In essence, an image should only be deleted if a) it violates existing policies (referencing, fan work, etc.) or b) if it's exactly the same image as a pre-existing one.


All images uploaded to the wiki should indicate the conditions and/or licenses that govern its use somewhere in the description. Images that cannot be legally used maybe removed without warning. The wiki has templates for copyright- and/or license-labelling purposes of which some are described below. All may be found in Category:Image copyright templates.


  • Usage: {{ImgCPBlizzard}}
  • Intended for material taken from directly from Blizzard Entertainment.
  • This may include material from Blizzard websites, such as concept art and videos.
  • This does not include screenshots or camera shots taken by users of Blizzard work. These fall under fair use.
  • Blizzard permits this material to be used under certain conditions (Blizzard Legal FAQ).



  • Usage: {{ImgCPFairUse}}
  • Intended for material that may be used under the tenants of fair use.
  • Be careful: fair use is not a catch-all for any material lacking discrete terms of use by the copyright holder.


  • Usage: {{ImgCPScreenshot}}
  • Intended for screenshots of copyrighted video games (StarCraft series).
  • Material directly from Blizzard goes under Template:ImgCPBlizzard instead.


  • Usage: {{ImgCPCover}}
  • Intended for cover art of Blizzard-licensed work. This may include cover work from
    • Novels
    • Graphic novels
  • The use of this material must adhere to fair use.


  • Usage: {{ImgCPFreeUse}}
  • Intended for material whose copyright holder has allowed the unlimited reuse of by all parties.


  • Usage: {{ImgCPComic}}
  • Intended for material from a comic book or graphic novel that may be used under the tenants of fair use.
  • Be careful: fair use is not a catch-all for any material lacking discrete terms of use by the copyright holder.


  • Usage: {{ImgCPPubDom}}
  • Intended for material which has been released into the public domain or whose copyright has expired.


Each image must have a description containing:

  • An overview of the image ("what are we looking at?")
  • Name of the artist ("who made it?")
    • For screenshots, this is not the person who took the screenshot. This is the creator of the original.
  • Name of the copyright holder if the artist is not the copyright holder
  • Source ("where is it from?")
    • If a screenshot was taken personally by the user, the source is the source program.
    • If an image was taken from another site, the source is the webpage with the image.


Images should be renamed in a descriptive fashion before being uploaded. This makes it easier to locate wayward images in the unused files list, in addition to aiding general identification.

Buildings and UnitsEdit

Building and unit images should take the following format:


Invalid language.

You need to specify a language like this: <source lang="html4strict">...</source>

Supported languages for syntax highlighting:

4cs, 6502acme, 6502kickass, 6502tasm, 68000devpac, abap, actionscript, actionscript3, ada, algol68, apache, applescript, apt_sources, arm, asm, asp, asymptote, autoconf, autohotkey, autoit, avisynth, awk, bascomavr, bash, basic4gl, bf, bibtex, blitzbasic, bnf, boo, c, c_loadrunner, c_mac, caddcl, cadlisp, cfdg, cfm, chaiscript, cil, clojure, cmake, cobol, coffeescript, cpp, cpp-qt, csharp, css, cuesheet, d, dcl, dcpu16, dcs, delphi, diff, div, dos, dot, e, ecmascript, eiffel, email, epc, erlang, euphoria, f1, falcon, fo, fortran, freebasic, freeswitch, fsharp, gambas, gdb, genero, genie, gettext, glsl, gml, gnuplot, go, groovy, gwbasic, haskell, haxe, hicest, hq9plus, html4strict, html5, icon, idl, ini, inno, intercal, io, j, java, java5, javascript, jquery, kixtart, klonec, klonecpp, latex, lb, ldif, lisp, llvm, locobasic, logtalk, lolcode, lotusformulas, lotusscript, lscript, lsl2, lua, m68k, magiksf, make, mapbasic, matlab, mirc, mmix, modula2, modula3, mpasm, mxml, mysql, nagios, netrexx, newlisp, nsis, oberon2, objc, objeck, ocaml, ocaml-brief, octave, oobas, oorexx, oracle11, oracle8, oxygene, oz, parasail, parigp, pascal, pcre, per, perl, perl6, pf, php, php-brief, pic16, pike, pixelbender, pli, plsql, postgresql, povray, powerbuilder, powershell, proftpd, progress, prolog, properties, providex, purebasic, pycon, pys60, python, q, qbasic, rails, rebol, reg, rexx, robots, rpmspec, rsplus, ruby, sas, scala, scheme, scilab, sdlbasic, smalltalk, smarty, spark, sparql, sql, stonescript, systemverilog, tcl, teraterm, text, thinbasic, tsql, typoscript, unicon, upc, urbi, uscript, vala, vb, vbnet, vedit, verilog, vhdl, vim, visualfoxpro, visualprolog, whitespace, whois, winbatch, xbasic, xml, xorg_conf, xpp, yaml, z80, zxbasic


Note the existence of underscores.  The <Extension> represents the extension of the image file type and is only included here for completeness. Aside from that the extension is irrelevant.

====Image Names====
This is the name of the primary focus of the image. There should be no spaces. Refer to the appropriate image categories to find names already in use.
: '''Marine'''_SC1_HeadAnim1
: '''Zealot'''_SC-G_Game1
: '''Zergling'''_SC2_Cncpt1
: '''Hive'''_SC1_Art1

This is an identifier for the StarCraft product the image came from.
{| border="1" cellpadding="2"
| '''Code''' || '''Product'''
| SC1 || [[StarCraft]]
| SC2 || [[StarCraft II]]
| SC-G || [[StarCraft: Ghost]]
| SC-BG || [[StarCraft: The Board Game]]
| SC-BG-BW || [[StarCraft: The Board Game: Brood War]]
| Alt-SC || [[Alternity: StarCraft Edition]]
| SC-FL''x''|| [[StarCraft: Frontline]], where ''x'' is the volume number. Add the specific source story in the file description.
| SC-Com''x'' || [[StarCraft (comic)]], where ''x'' is the issue number.
| SC-OGN || [[StarCraft (graphic novel)]]
| SC-GA''x'' || [[StarCraft: Ghost Academy]], where ''x'' is the issue number.

This identifies the nature of the image.
{| border="1" cellpadding="2"
| Art
| General 2D art from in-product sources. Use '''Rend''' for 3D art. Use '''Cncpt''' for concept art. Use '''Comic''' for comic or graphic novel art.
| Cine
|Art from cinematics.
| Cncpt
| Concept art.
| Comic
| Comic or graphic novel art.
| Game
| Static images of in-game objects from the '''final release'''. Use '''DevGame''' for images from in-development images.
| GameAnim
| Animations of in-game objects from the '''final release'''. Use '''DevGameAnim''' for images from in-development images.
| Head
| Static images of in-game unit profiles from the '''final release'''. Use '''DevHead''' for images from in-development images.
| HeadAnim
| Animations of in-game unit profiles from the '''final release'''. Use '''DevHeadAnim''' for images from in-development images.
| Icon
| Use for interface images, like abilities, upgrades, resources, etc..
| Map
| Full images of a StarCraft map. May also be used for minimaps.
| Rend
|General 3D art.
|Static images of story mode scenes from the '''final release'''. Use '''DevStory''' for images from in-development images.
| Phys
|Images of statues, toys and other physical objects.

Every type identifier should be followed by a number, as there may be multiple images of the same type. For example, a category might have images named as follows:
: Marine_SC1_Game1
: Marine_SC1_Game2
: Marine_SC1_Game3
: Marine_SC2_Game1
: Marine_SC2_Game2
: Marine_SC2_Game3
Note that the StarCraft II images are indexed independently of the StarCraft images.  Remember that since file extensions are irrelevant to the scheme, it is '''not''' permissible to have something as follows:
: Marine_SC-G_Game3.png
: Marine_SC-G_Game3.gif
The following would be correct:
: Marine_SC-G_Game3.png
: Marine_SC-G_Game4.gif

====File Extensions====
File extensions should be represented as a three letter, lower case, suffix (eg. gif, png, jpg, svg).

===Case Sensitivity===
Names are case sensitive. "Marine_SC1_Game1" is ''not'' the same as "Marine_SC1_'''g'''ame1" or "'''m'''arine_SC1_Game1". The latter two would be incorrect.

==Image Categories==
All images should be categorized within the [[:Category:Images]] [ tree]. Like articles, images may belong to multiple categories.

===Notable Categories===
: [[:Category:User images]]
:: This is for images that are used only on user pages. Images used in articles as well as user pages should not be placed here.

==Image Size==
Note that by image size we mean the amount of space it occupies in file storage space. Uploaded images should be smaller than 150kB each, and ideally they should be far smaller. We wish to avoid having to download multiple megabytes worth of images for an article to function. Ultimately the challenge is to minimize size while preserving sufficient quality for the image to be useful or aesthetically pleasing.

Images not intended for use in articles or to augment the wikis informational content, and exceed 150kB, may be subject to summary deletion without notice.

The following are some suggestions that may help.

If in doubt, images should be submitted in '''JPEG''' format. JPEG is a lossy compressed format which aims to reduce size by sacrificing some quality.
*Many image manipulation programs allow one to choose the 'quality' of a JPEG before saving, typically on a scale from 1 (lowest quality) to 100 (highest quality). One will need to try different quality settings and compare the results to the original image to determine the optimal balance. If in doubt start at 80 and adjust as needed. Remember: most images will appear as thumbnails so loss of quality will be less noticeable.
*If possible find the original image in a lossless format before converting to JPEG.
*If resizing or cropping a JPEG, to ensure minimum loss of quality either:
#Convert it to a lossless format first then reconvert it to JPEG, OR
#Use the GIMP and save directly to JPEG using the advanced option "Use quality settings from original image".

While JPEG is a good general purpose format, ''small'' images maybe submitted in '''PNG''' format.  PNG is a lossless compressed format which prioritizes quality. This can result in rather large sizes if the image has many pixels and a wide range of colors.
*Do '''not''' upload images in '''BMP''' format. BMP is lossless but does not use compression. Convert from BMP to PNG before uploading.
*Do '''not''' upload static (as opposed to ''animated'') images in '''GIF''' format. Savings can be had by converting GIF to PNG if one uses a program that gives the option to save 8-bit (as opposed to 24-bit) PNG images.
*Consider using utilities like [ pngcrush] or [ OptiPNG] to further compress PNG images.

===Animated Images===
Currently, most animated images are in '''GIF''' format. Other formats should be avoided as they are not well supported at this time. Some guidelines follow:
*Do '''not''' upload animated images larger than 300kB. If one cannot, somehow, slim it down than one will have to pick out the noteworthy frames within the animation and upload those separately.
*Animated images should only be used if the result is a noticeable and notable difference from a static image.

===Other Thoughts===
Still too large? Consider the following:
*The wiki is not an art gallery and does not need to include ultra-high resolution images. Upload a lower resolution version instead and give the original high resolution image as the source.
*Cut out parts of images that are not needed. Focus the image on the object(s) of interest.

==Helpful Templates==
* Usage: <nowiki>{{AttentionImage|Insert Reason Here}}</nowiki>
* Flags an image as requiring some sort of improvement.
* Usage: <nowiki>{{Delete|Insert Reason Here}}</nowiki>
* Nominates an image for deletion.

==General Help==

Adding images helps improve the quality of any given article, providing additional details and illustrating the subject - after all, a picture speaks a thousand words! - and can also improve a wiki search engine ranking.

The process of adding images to an article is very similar to adding videos. You can brush up on our video embed tool to complete your mastery of the tools of a wiki illustrator.

What are the requirements for adding images?

Both anonymous and registered users can add images to an article in source text editing mode. In visual editors, only registered users can.

Images must exist on the wiki. If they are not available, then they need to be uploaded first. Trying to add a non-existent image will only create a red link to a file page.

Only registered, logged-in users can upload files. See this page for details on uploading files.

How to add an image in a visual editor?

Whether you're editing with our new UCP editor, the legacy VisualEditor or classic rich-text editor, the process of adding an image to a page is rather similar. Every visual editor allows you to upload files. See this help page .

Remember: Only logged-in users can add and edit images through the wiki's Visual Editor.

UCP editor

  • After logging in, click the Edit or VisualEditor button on the page you want to add images to.
  • Once in Visual Editing mode, click on the Media button located on the top bar. This will open the Media Settings dialogue, where you can search for existing files according to their filenames or upload your own.
  • Once you have the image you want to add, click on it. The dialogue will expand the image and give you a little more information on it. Click use this image to continue.
  • The next dialogue allows you to customize how the image will appear on the page by adding a caption or alternative text (General tab) and deciding on its size, alignment, and appearance (Advanced tab).
  • Once finished, click Insert and then Save the page to commit your changes.

You can also edit images already present on the page by clicking on them and selecting the Edit button, which will open the same customization dialogue.

Legacy VisualEditor

If you prefer visual guides, the video at the top of the page shows how to add images using the legacy VE editor.
  • Log into your account, then click the VisualEditor button on the page you want to add images to.
  • Select the Photo button from the top bar. This will open the Insert an image dialogue box, where you can either search for existing images according to their filenames or upload new ones.
  • You can add multiple images to the page at once by selecting them in the dialogue box. Selected images will have a white checkmark over them. Once you've selected all of them, click Apply changes.
  • The files will be added to the page, aligned to the right and at the default width (220px). To customize the images, double-click on them. This will open a dialogue box that will allow you to customize them by adding a caption or alternative text (General tab) and deciding on its size, alignment, and appearance (Advanced tab).

Classic rich-text editor

Edit toolbar image upload2

This is where you go in the classic editor to add an image.


Finding an already-uploaded image in the classic editor.

Photo description

Here's where you add a caption and change the alignment or size of the image. Don't be confused by the fact that the screen says "upload photo" even though you're using an already-uploaded image.

  • Log in to your account, and then click on the Edit button on the page where you want to add an image.
  • Once in edit mode, click on the button labelled Photo Photo button on the right rail of the editor toolbar.
  • A pop-up will appear, which will allow you to search for photos already uploaded to the wiki or upload new ones.
  • Once you choose an image to add, click upload.
  • Next you will be able to adjust the size and placement of the photo. You can also add a caption, which will display below the photo.
  • Once done, click on the Add photo button to finish adding it to the article.
  • To commit changes, click Publish and your photo will be live on the page.

As in other editors, images already present on the page can be modified at any time. Simply hover over the image and choose modify, and the same pop-up window will appear.

How to add an image in source editing mode?

Source editing is fundamentally different from visual editors, as you directly edit the underlying wikitext. The image follows a specific format, enclosed in square brackets like a regular link.

[[File:Wiki.png|220px|center|thumb|link=Help:Adding images|alt=This is an alt text|And this a description]]

  • Every image on the page starts with File: or Image:, followed by the exact name of the uploaded file. It is case sensitive: Wiki.png and WIKI.png are considered different files.
  • If only the link is specified, the image will be added as is: At the base resolution and inline. To customize its appearance, you can add arguments, separated by the vertical bar or pipe symbol, |. These are:
    • Size, specified in pixels. For example, 220px will display the image at 220 pixels of width.
    • Alignment on the page. left and right will align the image to the left and right respectively, with text flowing around the image. center will align it to the middle of the page with no text flow around it.
    • Appearance. Adding thumb will cause the image to display as a thumbnail at a default width if it's not specified otherwise, with the description displayed beneath. You can also choose border to display the image with a border around it.
    • Link will cause the image to open a specific page, rather than its file description. It is always preceded by link=.
    • Alternative text, specified with alt=, which will show on mouseover or display if an image does not load.
    • Description, which will display below the image if it's specified to appear as a thumbnail or on mouseover. Any text that is not recognized by the wiki as an argument will be interpreted as a description.

The wiki software does not require the arguments to be added in any specific order, although it's considered good practice to use a consistent pattern. For more details on adding images via wikitext, see the image formatting section here. For linking to image description pages, see this page.

How to view the images at a higher resolution?

Image Lightbox

Viewing a photo from the lightbox

When placed on the page, images are typically presented at a much smaller resolution. You can inspect them by going to the file page or by opening them in the lightbox.

The lightbox opens by default when clicking on the image, with the link to the file description page displayed at the top of the lightbox.

If you want to bypass the lightbox entirely, simply hold "Ctrl" (for Windows users) or "Command" (for Mac users), then click on the photo. It will open a new tab, but you'll be on the file page in the new tab.


See also

Further help and feedback

Community content is available under CC-BY-SA unless otherwise noted.