You just got a mention in a major tech blog. Your startup is trending. You rush to update your Wikipedia page, hoping the new traffic sticks. But you hit a wall. The article looks bare. No logo. No product screenshots. Just text. Why? Because Wikipedia has strict rules about what images can appear on its pages, specifically regarding copyright and notability. Most companies fail here because they treat Wikipedia like their own website or social media feed. It isn't. It’s an encyclopedia.
If you want your brand represented visually, you need to understand three things: file format, licensing status, and context. This guide breaks down exactly how to get your logos and screens onto Wikipedia without getting deleted by an editor within minutes.
The Core Problem: Copyright vs. Notability
Here is the harsh reality: most corporate press kits are useless for Wikipedia. Why? Because they are copyrighted material owned by your company. Wikipedia generally requires content to be freely licensed (like Creative Commons) or public domain. If you upload a high-res JPEG of your CEO from your website, it gets flagged immediately.
There is one exception: Fair Use. Under US copyright law, limited use of copyrighted works for commentary, criticism, or news reporting is allowed. Wikipedia relies heavily on this doctrine for logos and low-resolution screenshots. However, Fair Use is not a blanket permission slip. It is a legal defense that must meet specific criteria. If your image doesn’t meet them, an editor will tag it with {{Non-free use rationale}} or delete it outright.
So, before you even think about uploading, ask yourself: Does this image add encyclopedic value? A screenshot of your app’s landing page might prove the interface exists, but a photo of your team at a hackathon might only matter if the event itself is notable.
Logos: The Low-Resolution Rule
Let’s start with the easiest win: your logo. You can use your official company logo on Wikipedia, but there are strict technical constraints. You cannot upload the massive SVG file you use for billboards. Wikipedia prefers raster formats like PNG or JPG for non-free content, though SVGs are increasingly accepted for free-licensed logos.
| Attribute | Requirement | Why It Matters |
|---|---|---|
| Format | PNG or JPG | SVG is preferred for free licenses, but non-free logos often require raster formats to prevent vector scaling issues in thumbnails. |
| Resolution | Low (typically < 100px wide) | High resolution implies commercial quality, which undermines the "Fair Use" argument. Small size proves it's for identification, not decoration. |
| Background | Transparent (PNG) | A white box around your logo looks unprofessional against Wikipedia’s clean interface. |
| Licensing | Non-free (Fair Use) | You retain copyright, but grant Wikipedia limited usage rights. |
When you upload your logo, you must fill out the description page carefully. Select "This is a non-free logo." Then, provide a rationale. Do not just write "Company Logo." Write something specific: "This low-resolution version of the Acme Corp logo is used to identify the subject of the article. No free equivalent exists. Using it does not replace the market value of the original artwork." That last sentence is critical. Editors look for it.
Screenshots: Proving Functionality
Logos are easy. Screenshots are tricky. Editors often debate whether a screenshot of your software adds enough value to justify a non-free license. To pass review, your screenshot needs to show something unique that text alone cannot describe.
Consider a SaaS platform. A generic screenshot of a login screen is weak. Everyone knows what a login screen looks like. Instead, capture a complex dashboard feature, a unique data visualization, or a user flow that defines your product. For example, if your tool uses AI to auto-tag photos, show the tagging process in action. That demonstrates functionality.
Technical specs matter here too. Crop out browser chrome (the address bar, tabs). Remove any watermarks. Ensure the text is legible. If your UI is cluttered, blur out sensitive user data. Wikipedia editors hate privacy violations. If you show a customer list, anonymize the names unless those customers are public figures mentioned elsewhere in the article.
Also, check the date. If your screenshot shows a version of your app from 2023, but you’re writing about the 2026 release, update it. Outdated visuals hurt credibility. When uploading, categorize it properly. Use categories like "Screenshots of [Software Name]" so other editors can find related images.
The Licensing Maze: CC-BY-SA vs. Fair Use
Not everything has to be Fair Use. In fact, Free Licensed images are better. They don’t carry the risk of deletion. If you have photos of your office, products, or events, consider releasing them under a Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.
What does this mean for you? It means anyone can copy, modify, and sell your image, as long as they credit you and share their modifications under the same license. Many brands fear losing control over their imagery. But think about the reach. A CC-licensed image of your product can end up in textbooks, news articles, and other wikis worldwide. That is free marketing.
To upload a CC image, you need proof of ownership. If you took the photo, you own it. If a photographer took it, you need a written release granting you the right to sublicense it under CC. Keep this document safe. Wikipedia may ask for it via OTRS (Open Ticket Request System) if someone challenges the upload.
Step-by-Step Upload Process
Ready to upload? Here is the workflow that minimizes rejection risks.
- Prepare the File: Resize your image. For logos, aim for 50-100 pixels wide. For screenshots, keep it under 800 pixels wide if possible. Save as PNG for transparency, JPG for photos.
- Check Existing Files: Search Wikimedia Commons first. Someone might already have uploaded a better version. Don’t duplicate effort.
- Upload to Wikimedia Commons: Even non-free files go through a specific process. For Fair Use images, you usually upload directly to the English Wikipedia site, not Commons. For CC images, upload to Commons.
- Fill the Metadata: This is where most people fail.
- Description: Be detailed. "Screenshot of Acme App v2.0 showing the AI tagging feature."
- Source: "Own work by author" or "Press Kit from Acme Corp website."
- Author: Your name or company name.
- Licensing: Select the correct template. For non-free, choose "{{Non-free use rationale}}" and fill in the fields for Article, Purpose, Replaceability, etc.
- Add Categories: Add relevant categories like "Company logos" or "Software screenshots." This helps editors find your file.
- Insert into Article: Go to your Wikipedia page. Edit the section where the image belongs. Use the syntax
[[File:Filename.png|thumb|Caption]]. Always add a caption that explains what the viewer is seeing.
Common Pitfalls That Get Images Deleted
Even with perfect files, you can still get slapped with a deletion notice. Here are the top reasons why.
- Orphaned Files: You uploaded the image but didn’t put it in an article. If it sits unused for seven days, it gets deleted. Always insert it immediately.
- Insufficient Rationale: Writing "Used for identification" is not enough. You must explain why no free alternative exists. If you say "It’s our logo," an editor will ask, "Why can’t we draw a simple vector icon instead?" Answer that question in the rationale.
- Copyright Violations: Did you take a screenshot that includes a third-party logo? If your app displays a Facebook login button, that’s another trademark. While minor, it complicates the rationale. Try to crop out third-party elements.
- Wrong License Claim: Don’t claim CC-BY if you haven’t released the rights. If you upload a stock photo thinking you own it, but you only bought a standard license, you’re lying to Wikipedia. Stock photos rarely qualify for CC.
Building a Visual Strategy
Don’t wait until you’re famous to worry about visuals. Start building a repository of free-licensed images now. Hire a photographer to shoot your product line and explicitly state in the contract that the images will be released under CC BY-SA. Over time, you’ll build a library of high-quality, safe-to-use assets.
For logos and key screenshots, maintain a "press kit" folder specifically formatted for Wikipedia. Keep low-res versions ready. Monitor your page. If an editor tags your image, read the talk page discussion. Engage politely. Explain your rationale. Often, a quick edit to the description saves the file.
Remember, Wikipedia is a community project. Editors are volunteers. They aren’t trying to block your marketing; they’re protecting the integrity of the encyclopedia. Respect the rules, provide clear metadata, and focus on educational value. Do that, and your visual assets will stay up, helping readers understand who you are and what you do.
Can I use my high-resolution logo on Wikipedia?
Generally, no. For non-free logos, Wikipedia requires low-resolution versions (usually under 100px wide) to support the Fair Use claim. High-resolution images imply commercial use, which conflicts with the non-commercial nature of the encyclopedia. Exceptions exist for very small icons or if the logo is released under a free license.
Do I need permission to use a screenshot of my own app?
Yes, technically. Even though you own the code, the visual design is copyrighted. You must grant Wikipedia a non-exclusive license to use it. If you own the copyright, you can self-license it as Fair Use or release it under Creative Commons. If a third party designed the UI, you need their permission.
What happens if my image is deleted?
If an image is deleted, check the deletion reason. It’s often due to missing rationale or copyright issues. You can request undeletion if you believe the decision was wrong, but you must fix the underlying issue first. Re-uploading the same file without changes will likely lead to immediate re-deletion.
Is a press photo considered Fair Use?
Rarely. Press photos are typically created for promotional purposes. Unless the photo depicts a historical event or a unique moment that cannot be replicated, it usually fails the "no free equivalent" test. Editors prefer free-licensed photos taken by enthusiasts or staff over staged press shots.
How do I handle logos with text?
Logos with significant text are harder to defend as Fair Use because the text can be transcribed. If the logo is purely typographic, an editor might argue that a text label is sufficient. Complex graphical logos are easier to justify than simple wordmarks.
