This page is considered anofficial guideline on Wikimedia Commons.
It illustrates standards or behaviors which most editors agree with in principle and generally follow. Feel free to update the page as needed, but please use thediscussion page to propose major changes.
This guideline is aboutwhen and how existing files can, should and should not be overwritten.[1] Such guidance is necessary because both Wikimedia projects using Commons files andexternal reusers who use content directly from Commons expect files to remain reasonably the same. Consequently, the basic rule is thatexisting files should not be overwritten with substantially different content. However,minor improvements may overwrite the previous version, subject to the exceptions noted below. In cases of uncertainty or inter-user disputes, a new file should be uploaded instead.
Following aVillage pump discussion in 2012, this guideline wasproposed and formally adopted as an RfC. A subsequent discussion in autumn 2023 found that many overwrites were not adhering to this guideline. It was thereforedecided to limit overwrite privileges for images to those who possess theautopatrol right (except for images uploaded by oneself andsome others). Editors seeking to overwrite files initially uploaded by others should request theautopatrol permission atCOM:Requests for rights. Those ineligible for autopatrol mayrequest an exception for a specific file.
[OK] =Overwrite existing file
=Upload as a new file[OK] Minor improvements Except for files used in Wikimedia projects where the use requires the file to remain unchanged Except for digital restoration Substantial changes or completely unrelated files Major changes Different files on the same topic Different files relating to the exact same object (building, statue, etc) Changes that reflect different data (e.g. updating a map), where the file has not been marked as updateable[OK] Unedited versions may be replaced by their uploader shortly after they are uploaded[OK] Secondary images may be replaced by their uploader shortly after they are uploaded[OK] Files marked as updateable (e.g. using the{{Current}} template) may be updated if appropriate[OK] Blurring, cropping or otherwise obscuringunfree elements and any other unacceptable parts (like sensitive personal information) that would otherwise result in deletion or adeletion request, provided that the file is still useful and inscope after the offending element has been obscured. Controversial or contested changes Changes that break consistency with other images Changes to license[OK] Except where new file license would be more accurate for all file versions
Consult the creator or original uploader first as they are likely to do a better job of fixing issues Use caution with files that have been awarded a special status like Commons Featured PictureWhen not overwriting the existing file,changes should be uploaded under a new name (ideally similar to the old one), and the file description page should link to the original file and give credit to the original author(s).
[OK] As a general rule, use the link "Upload a new version of this file" only for relatively minor improvements. Examples include:
and similar things where the essential composition is not altered. This might include a minor crop, for example to remove a recently-added border (don't upload over with files that remove parts of historical images), but aggressive crops should usually be uploaded under a new name, such as "Old image name (crop).jpg".
Correction of minor errors will usually be considered a minor improvement. However, the more extensive the correction, the more likely that it is better to upload the corrected version as a new file (to avoid possible disagreements about whether the correction is appropriate, and potentially anupload war), and if necessary nominate the old file for deletion.
Note: a file withimage annotations will lose those annotations if the pixel dimensions change –seeHelp:Image-Annotator#Limitations. This is not a reason to split a file when making minor improvements, as the annotations can be re-entered.
Ifdigital restoration work is being done on a historical document or artwork, the restoration (no matter how minor) should always be uploaded under a new filename from the original file, providing a link back to the source on which it was based in the new file's "other versions" field. The changes that were made should also be documented in sufficient detail to reproduce them, if possible. This is best practice for restorations, because it allows users and subsequent restorers to follow the chain of improvements and to make detailed comparison with the originals. (However, if a restoration already performed to a file, for example, missed a dust spot, it is not necessary to have a new file for each small change in the restoration.) In some cases such original files are marked with{{Please-do-not-overwrite-original-files}}.
? Take care with files that have been awarded aspecial status likeFeatured Picture (or the equivalent on another Wikimedia project) as the status applies to a particular file version. Featured Pictures,Quality Images andValued Images will be identified on their file description pages using{{Assessments}}. (NB the special Commons status does not transfer to derivative files.) The image creator may make minor changes where they feel this would be uncontroversial wrt the promotional status (for example, removing dust spots or fixing a minor tilt). Potentially controversial changes should be discussed with members of the forum that promoted the image.
Filesused in Wikimedia projects where the use requires the file to remain unchanged – which means no overwriting at all: not for updates, minor improvements, or error corrections. Comments (including pointing out errors, and pointing to other versions) may freely be made in the Commons file description, but the file itself should not be overwritten. If necessary, upload a new version as a separate file. Such files should be marked with{{Please-do-not-overwrite-permanent-version}}.
Controversial or contested changes. If another editor thinks that the change is not an improvement (even if the editor making the change deems it minor), the change can be reverted, and the new image should be uploaded under a new file name.See below.
The original image creator is often the best person to make edits. Since JPG is a lossy format, every edit to a JPG can deteriorate the image slightly; seemingly minor and "beneficial" edits such as changing white balance or adding noise reduction can actually do significant damage. Often the image creator has access to the RAW files from which to make a new version with whatever fix is required. This is always superior to editing the JPG. If it is a photograph, the image creator was there when the picture was taken so will be in a better position to judge whether colours and lighting are correct. Therefore it is strongly recommended that users wishing to make improvements to photographs first contact the creator, whether on Commons or elsewhere.
[OK] Sometimes users uploading new files that have been edited (e.g. a photograph improved for colour, contrast, etc., compared to the raw photo) may wish to provide the original unedited version as well. Uploading these independently would needlessly clutter categories. The solution is to first upload the unedited version, and then shortly afterward to upload the edited version over it, so that the unedited version is available in the file history. The unedited versions are not intended to be used independently, and should not be split out as separate files unless this is needed for a specific known use. Files using this approach should be labelled with{{Unedited version}}.
Note: overwriting unedited versions applies only shortly after upload of the unedited version, and only to the original uploader when uploading an improved version of the same file. In all other cases, the usual criteria about overwriting (is it minor improvement?, etc.) apply. In addition, the usual rule about resolving disagreements applies: if another user feels it useful to split the file, it should be split.
[OK] Sometimes users may wish to provide an image related to their upload, which might fall outside theproject scope as an independent file. Examples include images of labels related to the subject of the main image, or the reverse of a postcard as evidence of copyright status. The solution is to first upload the secondary image, and then shortly afterward to upload the main image over it, so that the secondary image is available in the file history. The secondary images are not intended to be used independently, and should not be split out as separate files unless this is needed for a specific known use. Files using this approach should be labelled with{{Secondary image}}. Note that secondary images arenot exempt from the usual requirements ofCommons:Licensing.
Note: overwriting secondary images applies only shortly after upload of the secondary image, and only to the original uploader. In all other cases, the usual criteria about overwriting (is it minor improvement?, etc.) apply. In addition, the usual rule about resolving disagreements applies: if another user feels it useful to split the file, it should be split.
Be cautious about overwriting files with new versions reflecting new information, as in many cases this may not be what reusers want.
[OK] However, files may be identified to reusers as ones where information may be updated – these files can and should be overwritten to reflect new information as necessary. Identification may be by thefilename, file description,categories, or (most clearly) with the{{Current}} template. A file named "File:Germany location map.svg" is expected to indicate the current boundaries, and is expected to be updated if, for example, the boundaries changed or errors were observed. On the other hand a file named "File:Germany, Federal Republic of location map October 1949 - November 1950.svg" is expected to be correct for that period and not reflect current boundaries.
Digital restoration Files that have been awarded a special status likeCommons Featured Picture,Commons Quality Image, or similar status on another Wikimedia project. Such files are marked with{{Assessments}}. Files used in Wikimedia projects where the use requires the file to remain unchanged Controversial or contested changes –see below. Artificially upscaling or enlarging using any tool, including AI-based or deep learning services Removing parts of historical images.For instance, historical engravings often have a border, and text describing the image under the image. If it was part of the original composition, and you want to remove it for some use on Wikimedia sites, upload it as a new file. If there are annotations or markings in the image that weren't part of the original composition, these can be removed and placed into the{{Information}} template, without a need to upload as a new image; for example, in the case of the Bundesarchive images, there is usually a call number and date of the photograph. Major changes (e.g. a radical crop) Changes that reflect different data (e.g. updating a map)[OK] unless the file is marked as updateable – i.e. identified to reusers as one where information may be updated, by the filename, description, or with the{{Current}} template Completely unrelated files Different files on the same topic (such as a photo of a cow uploaded over another photo of a cow) Different files relating to the exact same object (e.g. a different photo ofMichelangelo's David) Changes to a file that are likely to be contested should be uploaded to a separate filename. Upload wars (a form ofedit war in which contributors repeatedly upload different versions of a file in an effort to have their version be the visible one) are always undesirable. As with other forms of edit warring, users who engage in upload wars may beblocked from editing.
If another editor thinks that a change is not an improvement (even if the editor making the change thinks it's minor), the change can be reverted. Once a change has been reverted, the new image should be uploaded under a new filename (unless the reverting editor explicitly or implicitly agrees to the contested change). This is true even if the change is necessary, in one editor's view, to avoid a copyright infringement: in this case, if agreement cannot be reached through discussion, the old file should be nominated for deletion.
The more known uses of a file there are (through transclusions on Wikimedia projects), the more cautious contributors should be in deciding whether a change qualifies as "minor". Widespread usage of a file makes it more likely that even small changes will be controversial. If in doubt, uploading as a separate file avoids potential surprises for reusers. In some cases, prior discussion with previous uploader(s) or in locations where the file is in use may help decide whether a planned change can be considered "minor".
When images are consistent among each other, individual images should not be changed in a way that makes them inconsistent with the others. (E.g.,File:Icosahedron flat.svg should not have been overwritten with a white version, because that broke the consistency ofthe set.)
[OK] Small changes can be made to all images, as long as they remain consistent. (E.g., it was fine to remove circles around numbers inFile:Hawaiian Eruption-numbers.svg, because it was done to all images inthe set.)
See for example the version histories of
Minor improvements for textual elements include correcting spelling on a map's labels. By contrast, translating a map's labels from English to German is a major change, and should be uploaded as a separate file.
Whether a crop is "substantial" depends partly on the proportion of the image cropped, and partly on how much the excluded content affects the composition. For an image of a museum object on a grey background, cropping much closer to the object was considered a minor crop:
.jpg)
On the other hand, the photograph below of Martin Scorsese was substantially cropped for a closeup on his face, and the result was put into a separate file; and the photograph below of a mountain was cropped to substantially recompose it:
.jpg)
.crop.jpg)
When cropping aJPEG image, remember to always uselossless cropping.
Examples:
Be sure to attribute the original author appropriately, and to apply a license compatible with the original file. You can use{{Derived from}} and{{Derivative versions}} to link the files. More specific derivative templates are also available, including{{Image extracted}},{{Retouched picture}}, and{{Attrib}}.
The template{{Information}} has an|other versions parameter which you can use to link between different versions of a file. You can
When you want to provide or use a stable link from the other projects for any image which is anticipated to be repeatedly updated, you have several ways to do it:
Warning: when doing one of these solutions, be sure that users of the filename are clear that the content of the file may change, and try to check uses of the file before updating the redirect or overwriting the file.
_-_n._1764.jpg){kind=link}
{{helpme}} onyour talk page, a volunteer will visit you there as soon as possible!