Metopedia file and media standards require uploaded files to be identifiable, lawful, accessible, and relevant to the page where they appear. Files are part of the evidentiary record. They must not be treated as decorative clutter or unsourced attachments.

Upload rule

Metopedia file and media standards
Type	Upload and media standard
Applies to	File uploads, screenshots, diagrams, charts, PDFs, documents, audio, video, datasets, image analysis outputs, and file pages
Core rule	Every file must have enough source, license, authorship, description, and context for readers to know what it is and why it appears on Metopedia.
Related pages	Metopedia:Copyrights, Metopedia:Accessibility standards, Metopedia:Digital evidence standards, Metopedia:Source standards

A file may be uploaded when it serves at least one of these purposes:

preserves evidence;
illustrates a method;
documents a source state;
supports a fact check;
explains a technical or historical point;
provides a chart, diagram, table, or visual comparison;
preserves a public-domain or open-license source;
supports a policy, help, or standards page.

Do not upload files for personal storage, private sharing, unrelated decoration, harassment, spam, malware, doxxing, or copyright evasion.

Required file-page metadata

Every uploaded file page must include the following information when available:

Field	Requirement
Description	What the file shows or contains.
Source	URL, DOI, archive, public record, author-created status, scan source, or upload origin.
Author or creator	Person, institution, account, photographer, agency, software, or unknown status.
Date	Creation date, publication date, capture date, upload date, or unknown status.
License	Public domain, Creative Commons, fair use, permission, site-owned, or restricted use.
Use rationale	Why the file is needed on Metopedia.
Alterations	Cropping, resizing, annotation, OCR, conversion, compression, redaction, enhancement, or analysis.
Accessibility description	Alt text, caption, transcript, or nearby description when the file carries meaning.
Evidence status	Original, copy, screenshot, processed derivative, archive, recreated chart, or illustrative diagram.

Recommended file description structure:

== Summary ==
Description: 
Source: 
Author: 
Date: 
Evidence status: 
Alterations: 
Accessibility description: 

== Licensing ==
License: 
Rationale: 

== Integrity ==
Original filename: 
SHA-256: 
Archive:

File names

File names must be descriptive. They must help future editors and readers understand the file without opening it.

Good:

Figshare-account-disabled-notice-2026-04-21.png
Apollo-17-GPN-2000-001137-light-analysis-comparison.png
Metopedia-privacy-policy-retention-table-2026.png

Weak:

image.png
Screenshot 2026-05-14.png
final2really.png
unknown.jpg

Use dates when the date is evidentiary. Use source identifiers when they matter. Avoid exaggerated conclusions in filenames unless the file itself is a page title or formal document.

Captions

Every meaningful image used in an article requires a caption. A caption must identify what the reader is looking at and why it matters.

A good caption answers:

what is shown;
where it came from;
when it was captured or created if relevant;
what page claim it supports;
whether it has been cropped, annotated, or processed.

Good:

Screenshot of the Zenodo tombstone for record 10.5281/zenodo.6536389, showing the removal reason listed as “Spam.” Captured May 14, 2026.

Weak:

Zenodo thing.

Alt text and accessible descriptions

Images that carry information require accessible descriptions. W3C accessibility guidance states that images require text alternatives that describe their information or function.^[1]

For simple images, a concise caption may provide enough context. For charts, diagrams, screenshots, and comparison images, add surrounding text that explains the important information.

Use:

concise alt text for simple images;
longer descriptions for charts and diagrams;
transcription for screenshots containing important text;
real text instead of image-only text where possible.

Screenshots

Screenshots must be treated as evidence captures. They require context.

Include:

source URL or platform;
date/time captured;
browser/device if relevant;
visible account context when relevant and safe;
whether the screenshot was cropped or annotated;
archive link when available;
transcription of important text;
redaction note.

Do not upload screenshots containing passwords, session cookies, private tokens, private addresses, or unrelated personal messages.

Charts and diagrams

Charts must be understandable without visual guesswork.

Requirements:

chart title;
source data;
axes labels;
units;
date range;
method used to generate chart;
caption explaining the main pattern;
accessible summary of the chart’s result.

Charts must not exaggerate scale, hide baselines without reason, use unlabeled axes, or convert weak data into visual certainty.

PDFs and documents

PDFs, DOCX files, spreadsheets, XML files, and text documents may be uploaded when they preserve source material or support research.

A document file page must identify:

document title;
author;
date;
version;
source;
license or permission status;
whether the document is original, exported, scanned, OCR-processed, or converted;
whether a text transcript is available.

When a PDF is central to a page, summarize the relevant content in the article. Do not force readers to open a PDF to understand the page’s main claim.

Audio and video

Audio and video files require:

source;
creator;
date;
license;
duration;
format;
summary;
transcript or key excerpt where practical;
warning for disturbing, loud, flashing, or sensitive content;
note of edits or conversions.

Do not use audio or video as a substitute for written evidence when a transcript can be provided.

Datasets and code files

Datasets and code files require enough documentation to inspect or reproduce the result.

Include:

source;
creator;
date;
version;
format;
schema or column definitions;
license;
hash when important;
software needed;
processing steps;
output files produced.

For code packages, identify dependencies and execution instructions when relevant.

Processed and derivative files

Processed files include cropped screenshots, annotated images, OCR output, compressed images, enhanced images, resized figures, translated documents, charts created from data, and image-forensic outputs.

Rules:

preserve the original where possible;
label processed files as processed;
explain what changed;
do not present processed files as originals;
keep analysis outputs separate from raw evidence;
include tool names and settings when the processing affects interpretation.

Example:

This file is an annotated derivative of the original screenshot. Red boxes were added to identify the removal notice. The original unannotated screenshot is preserved separately.

Fair use and restricted material

Restricted or copyrighted files may be used only when the use is legally and editorially justified. The file page must include a rationale.

A fair-use rationale must explain:

the source and copyright holder when known;
the purpose of use;
why the file is needed;
why a free alternative is not sufficient;
how much of the work is used;
why the use does not substitute for the original market;
where the file is used on Metopedia.

Do not upload whole copyrighted books, articles, videos, or datasets unless permission, license, public-domain status, or another lawful basis applies.

Public-domain and open-license files

Public-domain and open-license files still require source and attribution.

Include:

original source;
license name;
license URL;
creator;
date;
modifications;
attribution text required by license.

Do not assume that a file is public domain because it appears online or because it was posted by a government-adjacent account. Verify the license.

Redactions

Redacted files must identify the redaction.

Acceptable redactions include:

private email addresses;
phone numbers;
home addresses;
account tokens;
unrelated private messages;
passwords;
sensitive security details;
names of uninvolved private persons.

Do not alter evidence silently. Use visible redaction blocks or state exactly what was removed.

Unsafe files

Metopedia must not host malware, exploit files, stolen credentials, private keys, active phishing kits, weaponized scripts, or files that create unnecessary security risk.

Security-related evidence may be described, hashed, screenshotted, or cited through sandbox reports instead of uploaded directly. When a suspicious file is discussed, include a warning and avoid direct download links unless there is a controlled research reason.

File deletion and replacement

Files may be replaced or removed when they are illegal, unsafe, private, malicious, incorrectly licensed, duplicative, irrelevant, or misleading. When a file is replaced, the file page must explain the replacement reason when lawful and safe.

Do not delete a file merely because it is disputed. Disputed evidence should normally be labeled, contextualized, or moved to an evidence record.

Media review checklist

Before using a file, verify:

the file has a clear name;
the source is identified;
the author is identified or marked unknown;
the license or rationale is present;
the page use is relevant;
the caption explains the file;
meaningful images have accessible descriptions;
private information is redacted;
processed files are labeled;
originals are preserved when possible;
important files have hashes;
the file does not create avoidable legal or security risk.

References

↑ W3C Web Accessibility Initiative, “Images Tutorial.” https://www.w3.org/WAI/tutorials/images/

[wai-images-1] W3C Web Accessibility Initiative, “Images Tutorial.” https://www.w3.org/WAI/tutorials/images/

[1]

Upload rule

Required file-page metadata

File names

Captions

Alt text and accessible descriptions

Screenshots

Charts and diagrams

PDFs and documents

Audio and video

Datasets and code files

Processed and derivative files

Fair use and restricted material

Public-domain and open-license files

Redactions

Unsafe files

File deletion and replacement

Media review checklist

See also

References