View source for Manual:Image administration

<languages/>
<translate>
<!--T:1-->
This article describes how MediaWiki handles and stores files, and gives some information on configuring.
</translate>

<translate><!--T:2--> This applies to images as well as to any other type of file that can be uploaded.</translate>
<translate><!--T:3--> All files are stored with a corresponding article in the "File:" namespace.</translate>
<translate><!--T:4--> Prior to MediaWiki 1.14, the "Image:" namespace was used instead.</translate>
<translate><!--T:5--> "Image:" is still retained as an alias for backward compatibility.</translate>

<translate>
== Upload and usage of images == <!--T:6-->

<!--T:7-->
See <tvar name=1>{{ll|Help:Images}}</tvar>

== Enable upload of images == <!--T:8-->

<!--T:9-->
To upload files, these conditions have to be met:

<!--T:10-->
# MediaWiki must have uploads enabled.</translate> <translate><!--T:11--> Set <tvar name=1>{{ll|Manual:$wgEnableUploads|$wgEnableUploads}}</tvar> to <tvar name=2>{{phpi|true}}</tvar>.</translate>
<translate>
<!--T:12-->
# The file type must be allowed.</translate> <translate><!--T:13--> More information: <tvar name=1>{{ll|Manual:$wgFileExtensions|$wgFileExtensions}}</tvar>.</translate>
<translate>
<!--T:14-->
# The user must be in a group with the "upload" right.</translate> <translate><!--T:15--> By default this is given to all logged-in users.</translate>

<translate>
<!--T:16-->
Uploads are done using <tvar name=1>[[Special:Upload]]</tvar>.
</translate>

'''<translate><!--T:17--> See <tvar name=1>{{ll|Manual:Configuring file uploads}}</tvar>, <tvar name=2>{{ll|Manual:MIME type detection}}</tvar> and <tvar name=3>{{ll|Manual:Adding support for new filetypes}}</tvar></translate>'''

<translate>
== Relevant parameters for file handling == <!--T:18-->

<!--T:19-->
These parameters are relevant:
</translate>

* {{ll|Manual:Configuration settings#Images|2=<translate><!--T:20--> Image configuration</translate>}}
* {{ll|Manual:Configuration settings#Paths|2=<translate><!--T:21--> Path configuration</translate>}}
* {{ll|Manual:Configuration settings#Uploads|2=<translate><!--T:22--> Upload configuration</translate>}}

<translate>
== Image thumbnailing == <!--T:23-->

<!--T:24-->
MediaWiki's [[<tvar name=2>Special:MyLanguage/Help:Images</tvar>|image syntax]] allows dynamic resizing and '''thumbnailing''' of images (see <tvar name=1>{{ll|Manual:Configuring file uploads}}</tvar> for general help on file uploads).

<!--T:25-->
Image thumbnailing requires either [[w:ImageMagick|ImageMagick]] or [[w:GD Graphics Library|GD library]] – neither are part of the default MediaWiki installation.
</translate>

=== GD ===
<translate>
<!--T:207-->
PHP comes with GD graphics library enabled by default. GD will not require any configuration or modification to be used. 

<!--T:27-->
[[<tvar name=1>Special:MyLanguage/Manual:Running MediaWiki on Windows#ImageMagick</tvar>|It is recommended to use GD on Windows systems]].
</translate>

<translate><!--T:203--> GD can be downloaded from <tvar name=1>https://libgd.github.io/</tvar>.</translate>
<translate><!--T:31--> In recent PHP versions this is not required.</translate>

=== ImageMagick ===

<translate>
<!--T:206-->
In MediaWiki, enable ImageMagick in <tvar name=1><code>LocalSettings.php</code></tvar> by setting <tvar name=2>{{ll|Manual:$wgUseImageMagick|$wgUseImageMagick}}</tvar> to <tvar name=3>{{phpi|true}}</tvar>.

<!--T:204-->
ImageMagick can be downloaded from <tvar name=1>https://imagemagick.org/</tvar>.

<!--T:208-->
Once ImageMagick is installed, you must enable ImageMagick and point MediaWiki to the <tvar name=1><code>convert</code></tvar> or <tvar name=2><code>convert.exe</code></tvar> program on your computer in <tvar name=3>{{ll|Manual:LocalSettings.php|LocalSettings.php}}</tvar> like this:
</translate>

<syntaxhighlight lang="php">
$wgUseImageMagick = true;
#$wgImageMagickConvertCommand = 'C:/ImageMagick/convert.exe'; # for Windows
$wgImageMagickConvertCommand = '/usr/bin/convert'; # for Linux
</syntaxhighlight>

<translate><!--T:32--> If you use ImageMagick, set <tvar name=1>{{ll|Manual:$wgUseImageMagick|$wgUseImageMagick}}</tvar> to <tvar name=2>{{phpi|true}}</tvar> in <tvar name=3>LocalSettings.php</tvar>.</translate>
<translate><!--T:33--> Make sure that the command is executable by the web server process.</translate>
<translate><!--T:34--> For example, Windows users will want to change the default to "C:\ImageMagick\convert.exe" (or similar).</translate>

<translate>
<!--T:35-->
To re-create old thumbnail files before you used ImageMagick you can use <tvar name=ThumbnailEpoch>{{ll|Manual:$wgThumbnailEpoch|$wgThumbnailEpoch}}</tvar>.

<!--T:36-->
If rendering fails silently, check and increase <tvar name=MaxShellMemory>{{ll|Manual:$wgMaxShellMemory|$wgMaxShellMemory}}</tvar>.
</translate>

{{tip|1=<translate><!--T:38--> See the help page on ''[[<tvar name=1>Special:MyLanguage/Manual:Common_errors_and_symptoms#Image_Thumbnails_not_working_and/or_appearing</tvar>|Image Thumbnails not working]]'' for troubleshooting.</translate>}}

<translate><!--T:39--> [<tvar name=url>http://graphicsmagick.org/</tvar> GraphicsMagick] can also be used as an alternative to ImageMagick.</translate>
<translate><!--T:193--> You will need to set <tvar name=1>{{ll|Manual:$wgCustomConvertCommand|$wgCustomConvertCommand}}</tvar> to the following.</translate>
<translate><!--T:41--> E.g.:</translate>

<syntaxhighlight lang="php">
$wgUseImageMagick = false;
$wgCustomConvertCommand = "gm convert %s -resize %wx%h %d";
</syntaxhighlight>

<translate>
== Image formats == <!--T:205-->

=== GIF === <!--T:42-->

<!--T:43-->
For thumbnailing GIF-''Animations'' under windows, you need to install ImageMagick as described above.

=== SVG === <!--T:44-->
</translate>
[[File:Wikimania 2016 Dynamic SVG for Wikimedia projects.pdf|thumb|<translate><!--T:187--> Wikimania 2016 presentation on Dynamic SVG</translate>]]

<translate><!--T:45--> MediaWiki supports SVG image rendering: if enabled, SVG images can be used like other image files — they will automatically be rendered as a PNG file and thumbnailed as needed on the fly.</translate>
<translate><!--T:46--> If you're on a shared host and no SVG renderer is pre-installed, you should probably ask your provider to install it for you.</translate>

<translate>
<!--T:47-->
To enable SVG support:

<!--T:48-->
# Allow upload of SVG files in the LocalSettings.php file: <tvar name=1><code>{{ll|Manual:$wgFileExtensions|$wgFileExtensions}}[] = 'svg';</code></tvar> Note that MediaWiki will refuse SVG files containing JavaScript, for security reasons.</translate>
<translate>
<!--T:50-->
#:If you get an error saying the file is corrupt, make sure {{<tvar name=1>ll|Manual:MIME type detection</tvar>|MIME type detection}} is working properly.</translate>
<translate>
<!--T:51-->
# Add <tvar name=SVGConverter><code>{{ll|Manual:$wgSVGConverter|$wgSVGConverter}}</code></tvar> to <tvar name=LocalSettings>{{ll|Manual:LocalSettings.php|LocalSettings.php}}</tvar> and set the renderer you want to use.</translate>
<translate>
<!--T:52-->
#:Available options are <samp>[[w:ImageMagick|ImageMagick]]</samp>, <samp>[<tvar name=1>https://php.net/Imagick</tvar> ImagickExt]</samp>, <samp>[[w:sodipodi|sodipodi]]</samp>, <samp>[[w:inkscape|inkscape]]</samp>, <samp>[[w:Apache Batik|batik]]</samp>, <samp>[[w:rsvg|rsvg]]</samp>, and <samp>[[<tvar name=2>Special:MyLanguage/imgserv</tvar>|imgserv]]</samp>.</translate>
<translate>
<!--T:53-->
#: For example:</translate> <syntaxhighlight lang=php inline>$wgSVGConverter = 'ImageMagick';</syntaxhighlight>
#*{{note|1='''<translate><!--T:54--> If the converter program is not in the system path, you have to specify the ''directory'' that contains the program using <tvar name=SVGConverterPath><code>{{ll|Manual:$wgSVGConverterPath|$wgSVGConverterPath}}</code></tvar>.</translate>'''.}}
<translate>
<!--T:55-->
#* [[w:librsvg|librsvg]] is fast but not very accurate.</translate> <translate><!--T:192--> It depends on a large number of libraries. To automatically install all these libraries, you may want to use a package manager.</translate> <translate><!--T:57--> The Wikimedia projects use rsvg.</translate>
<translate>
<!--T:60-->
#* [[w:Batik (software)|Batik]] is the most accurate SVG renderer available, although its [[w:anti-aliasing|anti-aliasing]] is sometimes suboptimal.</translate> <translate><!--T:61--> Its SVG parsing is more strict, causing it to reject "almost valid" SVG files that other renderers accept (e.g. <tvar name=1>[[commons:File:UbuntuCoF.svg]]</tvar>).</translate> <translate><!--T:62--> Batik relies on Java, and is much slower than rsvg, though this may not be a huge issue unless you're constantly adding SVG files.</translate> <translate><!--T:63--> See <tvar name=1>{{ll|SVG benchmarks}}</tvar>.</translate> <translate><!--T:64--> Requires a lot of work to get running, if not included in your distribution.</translate>
<translate>
<!--T:65-->
#* [[w:Inkscape|Inkscape]] also does an accurate job of SVGs, half the speed of rsvg, but was designed for interactive graphical use; however, it comes with inkview which is a viewer/converter program – it requires a writable home directory for the user it's run as.</translate> <translate><!--T:66--> Since it will be running as user <tvar name="1"><code>www</code></tvar> or something similar, it will try to create <tvar name="2"><code>.inkscape/</code></tvar> and <tvar name="3"><code>.gnome2/</code></tvar> directories in the corresponding home directory, and will fail silently, [<tvar name="4">https://bugs.launchpad.net/inkscape/+bug/376866</tvar> crash] or [<tvar name="5">https://bugs.launchpad.net/inkscape/+bug/1353797</tvar> hang indefinitely] if it is not able to.</translate> <translate><!--T:67--> Inkscape is preferable to rsvg (a) on Windows (it comes as a standalone package) or (b) if you have important SVGs drawn in Inkscape that do not render correctly in rsvg.</translate> <translate><!--T:68--> Inkscape has as complicated a dependency chain as librsvg — use only if it's in your distribution or available as a complete standalone package.</translate>
<translate>
<!--T:69-->
#* [[w:Sodipodi|Sodipodi]] is the program Inkscape was forked from.</translate> <translate><!--T:70--> The same considerations apply. Sodipod is no longer under active development.</translate>
<translate>
<!--T:71-->
#* Since version 6.x.x [[w:ImageMagick|ImageMagick]] renders SVGs, but imperfectly.</translate> <translate><!--T:72--> This is the default, but avoid it if possible.</translate> <translate><!--T:73--> However, it does work.</translate><!--Is this still an up-to-date-information? If so, what is the buggy behaviour? -- Still so with imagemagick 6.6.1, resulting images have broken shapes & colours are way off --Richlv --> <translate><!--T:74--> On Windows, $wgConvertPath must be set to avoid a conflict with Windows' own convert.exe.</translate> <translate><!--T:75--> One simple alternative in this scenario is to add to LocalSettings.php the line <tvar name="1"><syntaxhighlight lang=php inline>$wgSVGConverters['ImageMagick'] = '"' . $wgImageMagickConvertCommand . '" -background white -thumbnail $widthx$height^! $input PNG:$output';</syntaxhighlight></tvar>, which also allows for spaces in the path.</translate>
<translate>
<!--T:196-->
#** To prevent thumbnail creation errors with ImageMagick, if it's ≥ 7.0.9-25, then Inkscape must also be ≥ 1.x.x. Likewise, if ImageMagick is < 7.0.9-25, then Inkscape must also be < 1.x.x.</translate> <translate><!--T:197--> See [<tvar name=1>https://github.com/ImageMagick/ImageMagick/issues/2062</tvar> ImageMagick issue].</translate>
<translate>
<!--T:76-->
#* The [<tvar name="1">https://php.net/Imagick</tvar> PHP Imagick extension] supports SVG rendering, however the same considerations as for the regular ImageMagick apply.</translate>
<translate>
<!--T:77-->
#* The [[w:GD Graphics Library|GD library]] is not capable of converting SVG images to the PNG format, at least according to Joen Asmussen's June 2008 [<tvar name=url>https://web.archive.org/web/20160317163820/https://moc.co/2008/06/converting-svg-to-png-on-the-fly-how/</tvar> NoScope] blog.</translate>
#* <translate><!--T:213--> [<tvar name=url>https://caniuse.com/svg</tvar> Over 98% of web browsers have at least basic support for displaying SVG files directly], but MediaWiki does not use that by default.</translate><ref group="notes"><translate><!--T:210--> Wikimedia sites also do not rely on client-side rendering, despite a request to do so, <tvar name=phab>{{phabricator|T5593}}</tvar>.</translate></ref> <translate><!--T:211--> Without the <tvar name=1>{{ll|Extension:NativeSvgHandler|NativeSvgHandler}}</tvar> extension, MediaWiki only supports client-side rendering in <tvar name=2>{{ll|MediaWiki 1.41}}</tvar> (released December 2023) and newer, by setting <tvar name=3><code class="mw-highlight">{{ll|Manual:$wgSVGNativeRendering|$wgSVGNativeRendering}} = {{#tag:span|true|class=k}}</code></tvar>.</translate>
<translate>
<!--T:81-->
Set <tvar name=1><code class="mw-highlight">{{ll|Manual:$wgSVGConverter|$wgSVGConverter}} = {{#tag:span|false|class=k}}</code></tvar> if SVG rendering is not needed and you wish to make your users download the svg file in order to view it.

==== Troubleshooting ==== <!--T:188-->
</translate>
<translate><!--T:189--> If you see a blank square instead of SVG (Chrome) or no image at all (Firefox) and all PNG links lead to 404 error and you don't see any other error message anywhere please check <tvar name=1>{{wg|GenerateThumbnailOnParse}}</tvar> variable.</translate>
<translate><!--T:190--> Setting it to <tvar name=1>{{phpi|false}}</tvar> may make SVG transformation deferred always.</translate>
<translate><!--T:198--> Make sure that <tvar name=1>[https://php.net/proc-open proc_open]</tvar> and <tvar name=2>[https://php.net/symlink symlink]</tvar> PHP methods are enabled (they may be disabled in php.ini for security or performance reasons).</translate>

<translate>
===JPEG (using GD)=== <!--T:82-->

<!--T:83-->
Simply adding the following line to LocalSettings.php will cause auto fall back to the GD library:
</translate>

<syntaxhighlight lang="php">
$wgUseImageMagick = false;
</syntaxhighlight>

<translate>
<!--T:84-->
For errors with JPEG thumbnails, see [[<tvar name=1>Special:MyLanguage/Manual:Errors and Symptoms#JPEG (using GD)</tvar>|JPEG (using GD)]].

===TIFF=== <!--T:85-->

<!--T:86-->
Generating thumbnails of TIFF files requires MediaWiki 1.15.0 or newer.

<!--T:87-->
# Allow upload of TIFF files in the LocalSettings.php file:</translate> <code>{{ll|Manual:$wgFileExtensions|$wgFileExtensions}}[] = 'tif';</code>
<translate>
<!--T:88-->
# Add <tvar name=1><code>{{ll|Manual:$wgTiffThumbnailType|$wgTiffThumbnailType}}</code></tvar> to <tvar name=2>{{ll|Manual:LocalSettings.php|LocalSettings.php}}</tvar> and set to either jpg or png to specify which type of thumbnail you wish to have generated.</translate>
<translate>
<!--T:89-->
# Making thumbnails of TIFF files may require system resources beyond those needed for thumbnailing JPEG, GIF, or PNG files.</translate> <translate><!--T:90--> Consider appropriate settings for <tvar name=1><code>{{ll|Manual:$wgMaxImageArea|$wgMaxImageArea}}</code></tvar> and <tvar name=2><code>{{ll|Manual:$wgMaxShellMemory|$wgMaxShellMemory}}</code></tvar></translate>

=== DjVu ===

{{See also|Manual:How to use DjVu with MediaWiki|ll=TRUE}}

<translate>
== Deletion of images == <!--T:92-->
</translate>
<translate><!--T:93--> Files, like wiki pages, can only be deleted by users with the <tvar name=1><code>{{int|Right-delete}}</code></tvar> (delete)" permission (<tvar name=2>{{lcfirst:{{int|Group-sysop}}}}</tvar> by default).</translate>
<translate><!--T:94--> Deletion of files is done by deleting the associated description page (or by clicking the <tvar name=1><code>{{int|Filehist-deleteall}}</code></tvar> link in the <tvar name=2><code>{{int|Filehist}}</code></tvar>" table).</translate>

<translate>
==== Deletion of individual revisions ==== <!--T:95-->
</translate>
<translate><!--T:96--> If a file has been altered, there is a revision history of the files which is displayed on the file article page.</translate>
<translate><!--T:97--> Each revision has a <tvar name=1><code>{{int|Filehist-deleteone}}</code></tvar> link.</translate>
<translate><!--T:98--> If this is clicked, the revision and the file are deleted.</translate>

{{Note|1=<translate><!--T:99--> The versions of files are separate from the page history of the file description page.</translate>}}

<translate>
<!--T:100-->
Information about old revisions of ''files'' are stored in the <tvar name=oldimage>{{ll|Manual:oldimage table|oldimage}}</tvar> table while information on old revisions of the ''pages'' are stored in the <tvar name=revision>{{ll|Manual:revision table|revision}}</tvar> table.

=== Undeleting files === <!--T:101-->
</translate>
<translate><!--T:194--> Files can be undeleted in exactly the same way as normal wiki pages.</translate>
<translate><!--T:195--> The directory in which deleted files are stored is defined by <tvar name=1>{{ll|Manual:$wgDeletedDirectory}}</tvar>.</translate>
<translate><!--T:106--> Information about deleted images are stored in the <tvar name=1>{{ll|Manual:Filearchive table|filearchive}}</tvar> table.</translate>

<translate>
=== Deletion of Archived Files === <!--T:107-->
</translate>
<translate><!--T:108--> Since MediaWiki version 1.11, deleted images are still stored on the server by default.</translate>
<translate><!--T:109--> If you want to delete selected archived images, you can do so using the <tvar name=eraseArchivedFile>{{ll|Manual:eraseArchivedFile.php|eraseArchivedFile.php}}</tvar> maintenance script.</translate>
<translate><!--T:110--> If you want to delete all of them completely, you can do that with the <tvar name=deleteArchivedFiles>{{ll|Manual:deleteArchivedFiles.php|deleteArchivedFiles.php}}</tvar> script.</translate>
<translate><!--T:111--> If you delete archived files, you can not undelete those files anymore.</translate>

<translate>
=== Reasons for Deleting a File === <!--T:112-->
</translate>
<translate><!--T:113--> When choosing to delete a file, as described [[<tvar name=1>#Deletion of images</tvar>|above]], users will be asked to provide a reason for deletion.</translate>
<translate><!--T:114--> The available reasons can be edited on the <tvar name=1>[[MediaWiki:Filedelete-reason-dropdown]]</tvar> of your wiki.</translate>

<translate>
== Data storage == <!--T:115-->

<!--T:116-->
Whenever an image is uploaded, several things are created:

<!--T:117-->
# An article in the file namespace with the name of the file, e.g. File:MyPicture.png.</translate> <translate><!--T:118--> This page is stored and can be edited like any other page.</translate>
<translate>
<!--T:119-->
# The file itself is stored in a folder on the file system with whitespaces merged and replaced with <tvar name=1><code>_</code></tvar>. </translate>
<translate>
<!--T:120-->
# If necessary and thumbnailing is available, thumbnailed versions of the file will be created when necessary (such as for the usage on the file description page).</translate> <translate><!--T:121--> These are stored in the thumb directory of the image directory, in a separate directory for each main file.</translate>

<translate>
<!--T:122-->
If <tvar name=HashedUploadDirectory>{{ll|Manual:$wgHashedUploadDirectory|$wgHashedUploadDirectory}}</tvar> is enabled (by default), MediaWiki creates several subdirectories in the images directory.

<!--T:123-->
The directory names are from the first two characters of the md5 hash of the final filename.

=== Folders === <!--T:124-->

<!--T:125-->
All image files are stored in a folder determined by <tvar name=UploadPath>{{ll|Manual:$wgUploadPath|$wgUploadPath}}</tvar> (<tvar name=path><code>images/</code></tvar>, by default).

<!--T:126-->
Description of named image subfolders:
</translate>

; archive
: <translate><!--T:127--> This is the storage place for files that have been replaced by newer versions.</translate>
; temp
: <translate><!--T:128--> Used for temporary storage of files during image uploading.</translate> <translate><!--T:129--> (Due to <tvar name=bug>{{phabricator|T11018}}</tvar>, these files may not always be automatically deleted).</translate>
; thumb
: <translate><!--T:130--> Thumbnails (automatically generated) for the files.</translate> <translate><!--T:131--> If these are deleted, they are automatically regenerated when needed.</translate>

<translate>
<!--T:132-->
Depending on the configuration, there may be additional image subfolders:
</translate>

; math
: <translate><!--T:133--> Folder to store your rendered TeX input, see also [[<tvar name=1>Special:MyLanguage/Extension:Math</tvar>|Extension:Math]] or [[<tvar name=2>Special:MyLanguage/Manual:Math</tvar>|Manual:Math]].</translate>
; x/xy
: <translate><!--T:134--> If <tvar name=1>{{phpi|$wgHashedUploadDirectory}}</tvar> is set to <tvar name=2>{{phpi|true}}</tvar> (which is the default), images will be stored in subfolders of the images, thus making file paths look like <tvar name="3"><code>images/a/ab/filename.jpg</code></tvar>.</translate> <translate><!--T:135--> See <tvar name=1>{{ll|Manual:$wgHashedUploadDirectory}}</tvar> for more details on why this might be desired and how this system works.</translate>

<translate>
=== Database tables === <!--T:136-->

<!--T:137-->
* The file description page is stored as any page in the page, text, revision etc. tables
</translate>
* {{ll|Manual:image table|image}} - <translate><!--T:138--> Holds some metadata such as the size of the file and the upload date.</translate>
* {{ll|Manual:oldimage table|oldimage}} - <translate><!--T:139--> This stores information for files that have been replaced with newer versions.</translate>
* {{ll|Manual:filearchive table|filearchive}} - <translate><!--T:140--> Holds the information on the deleted files.</translate>
* {{ll|imagelinks table|imagelinks}} - <translate><!--T:141--> Records what pages use a file.</translate>

<translate>
=== Space usage === <!--T:142-->
</translate>
<translate><!--T:143--> Files need considerably more space than articles.</translate>
<translate><!--T:144--> The following calculations assume a block size of 4KB with Linux/Unix servers.</translate>

<translate>
<!--T:145-->
The default setting is <tvar name=1><code class="mw-highlight">{{ll|Manual:$wgHashedUploadDirectory|$wgHashedUploadDirectory}} = {{#tag:span|true|class=k}}</code></tvar>.

<!--T:146-->
Space requirements for all directories:

<!--T:147-->
* image directories: 0-f/x0-f: max. 16*16 = 256 directories = 256*4 KB = 1024 KB</translate>
<translate>
<!--T:148-->
* archive directories: 0-f/x0-f: max. 16*16 = 256 directories = 256*4 KB = 1024 KB</translate>
<translate>
<!--T:149-->
* thumb directories: 0-f/x0-f: max. 16*16 = 256 directories = 256*4 KB = 1024 KB</translate>
<translate>
<!--T:150-->
* temp directories: 0-f/x0-f: max. 16*16 = 256 directories = 256*4 KB = 1024 KB

<!--T:151-->
Therefore, the basic amount of space needed without any images uploaded is 4 MB in theory (although the directories are created only when needed).

<!--T:152-->
For each file we need:

<!--T:153-->
* size of the original image file + 2 KB average overhead

<!--T:154-->
For files that need to be thumbnailed:

<!--T:155-->
* size of the created thumbnail(s) + 2 KB average overhead (each)</translate>
<translate>
<!--T:156-->
* directory for thumbnail (4KB) (each image has its own thumbnail directory)

<!--T:157-->
Examples:

<!--T:158-->
* image 20778 Byte png (small size, no thumb): 24 KB for the image: Total 24 KB</translate>
<translate>
<!--T:159-->
* image 123.000 Byte jpeg (big size, auto thumb): 124 KB for the image, 4 KB for the thumb directory, 64KB for the thumb: Total: 192 KB

=== File Access === <!--T:160-->
</translate>
<translate><!--T:161--> Uploaded files are generally served directly by the web server, not through MediaWiki.</translate>
<translate><!--T:162--> While there may be a minimal level of security through obscurity with path encryption (e.g. /c/c4/...) if <tvar name=1>{{ll|Manual:$wgHashedUploadDirectory|$wgHashedUploadDirectory}}</tvar> is set, the path can be calculated easily from the file name and does not provide true protection.</translate>

<translate>
<!--T:163-->
For limiting access to authorized users, see <tvar name=1>{{ll|Manual:Image authorization}}</tvar>.

== Upload form == <!--T:199-->

<!--T:200-->
See the [[<tvar name=1>Special:MyLanguage/Manual:Configuring file uploads#Configuring the upload form</tvar>|documentation on configuring the upload form]].

== Licensing == <!--T:164-->
</translate>
MediaWiki allows licenses to be added to files uploaded from the [[Special:Upload]] page.
The list of licenses that appear in the license selection dropdown can be edited on the [[MediaWiki:Licenses]] page by a sysop.

<translate><!--T:214--> The page should be a bulleted list of items, and can have sub-items.</translate>
Each item can have one or more parameters, with the parameter separated by the pipe character (<code>|</code>).

<translate><!--T:215--> To make headers/categories, use only one parameter in a list item.</translate>
<translate><!--T:216--> The text will be what appears in the dropdown list, and will appear greyed-out and unclickable.</translate>

<translate><!--T:217--> To add license options, two or more parameters are required.</translate>
<translate><!--T:218--> The first parameter will be the template name to use, without the double square brackets.</translate>
<translate><!--T:219--> The last parameter will be what appears in the dropdown list for that license.</translate>
<translate><!--T:220--> Any additional parameters between the first and last parameters will be passed as arguments to the template.</translate>
<translate><!--T:221--> When a license is selected, a preview of what it would look like on the final page is shown in the upload wizard.</translate>

Below is a simple example (not using real templates) of how [[MediaWiki:Licenses]] should be formatted:

<pre>
* no-lic|No license.
* Made by me:
** self-lic|And it can only be used on this wiki.
** self-lic|free=yes|And I allow it to be used anywhere.
* Made by someone else:
** pd-lic|It's in the public domain.
** copyright-lic|It's copyrighted.
** cc-lic|It uses some CreativeCommons license.
** cc-lic|by-sa|It uses the CC-BY-SA license.
</pre>

The above assumes each template ending in "-lic" exists, where some of those templates take positional arguments such as "by-sa" and others take named arguments such as "free=yes".
Selecting the "And I allow it to be used anywhere" option, for example, would add the following text to the page of the new file:

<pre>
<nowiki>{{self-lic|free=yes}}</nowiki>
</pre>

Sites like Wikipedia and WikiMedia Commons will also use the <code>subst:</code> tag, such as WikiMedia Common's usage of it below:

<pre>
** subst:Template 2|flickrreview|subst:uwl|Image from Flickr and I do not know the license
</pre>

"Template 2" is an actual template that will take two parameters (being template names) and surround them with double curly brackets so they get transcluded on the page of the new image.
"uwl" is a template, whose documentation requires using it with the "subst:" tag instead of directly.
<translate><!--T:222--> The above will result in the following being added to the uploaded file's page:</translate>

<pre>
<nowiki>{{flickrreview}}{{subst:uwl}}</nowiki>
</pre>

<translate>
<!--T:223-->
On Wikipedia, substitution is used in other ways, such as adding a timestamp with the license at the time of upload.

<!--T:174-->
For detailed real world example, see [[Wikipedia:MediaWiki:Licenses]] or [[Commons:MediaWiki:Licenses]].

== Foreign Repositories == <!--T:175-->
</translate>
<translate><!--T:176--> It is possible to access files stored in foreign repositories, without needing to upload them to the wiki, by setting the <tvar name=1>{{ll|Manual:$wgForeignFileRepos|$wgForeignFileRepos}}</tvar> array.</translate>
<translate><!--T:177--> This feature offers several possibilities:</translate>

<translate>
<!--T:178-->
* '''ForeignAPIRepo''' accesses files from a remote MediaWiki installation, such as [[commons:|Wikimedia Commons]], through its API</translate>
<translate>
<!--T:179-->
* <tvar name=2>'''ForeignDBRepo'''</tvar> accesses files through a database, and is useful for creating [[<tvar name=1>Special:MyLanguage/Manual:Wiki family</tvar>|wiki families]]</translate>
<translate>
<!--T:180-->
* '''FSRepo''' accesses files from a local folder
</translate>

<translate><!--T:181--> In all cases, one would be able to embed files into a page using ordinary [[<tvar name=1>Special:MyLanguage/Help:Images</tvar>|image]] syntax and specifying the name of the file in the foreign repository.</translate>
<translate><!--T:182--> Note that some of the above implementations are still experimental, and might not be suitable for production sites.</translate>

<translate>
== Notes == <!--T:212-->
</translate>
<references group="notes" />

[[Category:MediaWiki configuration{{#translation:}}|{{PAGENAME}}]]
[[Category:Upload{{#translation:}}]]