Commons:Village pump/Technical

Shortcuts: COM:VP/T • COM:VPT

• Community portal
  • introduction
• Help desk
• Village pump
  • copyright
  • proposals
  • technical
• Administrators' noticeboard
  • vandalism
  • user problems
  • blocks and protections

Welcome to the Village pump technical section

Technical discussion

Village pump/Technical

Bug reports

Code review

Tools

Tools/Directory

Idea Lab

This page is used for technical questions relating to the tools, gadgets, or other technical issues about Commons; it is distinguished from the main Village pump, which handles community-wide discussion of all kinds. The page may also be used to advertise significant discussions taking place elsewhere, such as on the talk page of a Commons policy. Recent sections with no replies for 30 days and sections tagged with {{Section resolved|1=--~~~~}} may be archived; for old discussions, see the archives; recent archives: /Archive/2026/03 /Archive/2026/04.

COMMONS DISCUSSION PAGES

• Commons Help desk
• Village pump (general discussion)
  • Copyright
  • Proposals
  • Technical
• Graphics and photography discussion
  • Photography critiques
  • Image improvement
    • Illustration workshop
    • Map workshop
    • Photography workshop
    • Video and sound workshop
• Categories for discussion
• Undeletion requests
• Deletion requests
• Volunteer Response Team/Noticeboard
• Translators' noticeboard
• Work requests for bots

---

• Contact administrators
  • Vandalism
  • User problems (Dispute resolution)
  • Blocks and protections
• Bureaucrats' noticeboard
• CheckUser requests
• Oversight requests

---

• Telegram
• IRC ^webchat
• Commons mailing list (archive)
• Commons' bugs on Phabricator

Please note

• Feature or bug reports should be filed on Phabricator (see how to report a bug). Bugs with security implications should be reported differently (see how to report security bugs).
• Have you read the FAQ?
  
  

 

Start a new discussion

	SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 30 days.

Thumbnails not generating for external wikis

In the past several days, thumbnails are not being properly generated acrsso multiple wiki farms that use the wikimedia commons. Clicking through on the thumbnail returns a " Error Use thumbnail steps listed on https://w.wiki/GHai. Please contact noc@wikimedia.org for further information (a765913)"

Has something changed which has broken the standard functionality used by literally thousands of mediawiki wikis that rely on the wikimedia commons shard libraries? - 17:08, 7 March 2026 (UTC) Lestatdelc (talk) 17:08, 7 March 2026 (UTC)

@Lestatdelc, as stated in mw:Common thumbnail sizes#FAQ, the error is probably due to the wikis not using one of the "standard" thumbnail sizes. Previously, the thumbnail will generate for any specified size via URL, but now MediaWiki requires one of the "standard" size to be specified when requesting via URL.

However, this change was made in January 2026, so the problem might be something else if it only occurred in the past several days. Thanks. Tvpuppy (talk) 19:40, 7 March 2026 (UTC)

If you are using mw:Extension:QuickInstantCommons, please update to the latest version. I just recently (like last week) fixed a bug in it to make it compatible with these changes. Bawolff (talk) 10:19, 9 March 2026 (UTC)

And what if I don't want to use a "standard" thumbnail sizes? Then what? You used to be able to change the size of an SVG converted to PNG in the URL. Now you can't

Can't you stop fucking up the site holy shit??!!! First you ban 90% of the users from editing images and now this, what are you going to break next? Yilku1 (talk) 19:49, 14 March 2026 (UTC)

Please be civil and remember to be respectful to others. The change was implemented by MediaWiki and not by users here in Commons, but I certainly believe the change was made to improve the site rather than worsening it. Regarding your second point, I have no idea what you are referring to as I'm pretty sure "90% of the users" are not "banned from editing images". Thanks. Tvpuppy (talk) 20:04, 14 March 2026 (UTC)

I'm fucking tired of EVERYTHING enshittifing, and now it's happening to wikipedia. Who asked for this?

90% of the users can't edit images. You have to ask like a pleb to the admins so you can edit, but only one for the image you asked. Another stupid change nobody asked. Yilku1 (talk) 20:15, 14 March 2026 (UTC)

Explain me how breaking most thumbnails is improving the site? Yilku1 (talk) 03:08, 15 March 2026 (UTC)

If you are using instant commons (not quickinstantcommons) there is a setting you can set where it downloads the original and then resizes locally (to any size you want). Bawolff (talk) 20:40, 14 March 2026 (UTC)

Requesting bulk data cleanup - Scheer photos with credit in EXIF

Andrew Scheer, formerly leader of the opposition in Canada's parliament, has a Flickr stream that releases photos as CC-0, resulting in 1,901 files in Category:Files from Andrew Scheer's Flickr stream. When these files were uploaded from Flickr, since the account's under his name, Scheer was listed as the 'Author'. Poking around some of the files, I see many whose EXIF credits Andre Forget (e.g. File:088A0780 (41365002220).jpg with "Photos Andre Forget / OLO", where I assume OLO refers to Office of the Leader of the Opposition; another with slightly different credit is File:Andrew Scheer (40839023063).jpg).
Request: Is it possible to, in bulk, identify all of those which credit Andre Forget in the EXIF, and update him as the Author/Photographer of those images? Even though we don't need to credit the photographer as the files are CC-0, I think it's still worthwhile to credit the right person. -Consigned (talk) 01:32, 10 March 2026 (UTC)

I know we have bots that access EXIF data and act accordingly; given that Category:Files from Andrew Scheer's Flickr stream is not a large universe, certainly a bot could run over this data file-by-file and edit accordingly.

I don't think there is any user-facing way to search for particular content in EXIF data. - Jmabel ! talk 04:19, 10 March 2026 (UTC)

At worst, we could make sure the existing bot that extracts author info from EXIF data to SDC runs on all files in this category, after which I believe a Quarry query could find the relevant files. - Jmabel ! talk 04:21, 10 March 2026 (UTC)

Quarry can't access SDC, however it can access exif, so it should be posdible to get it to make a list. Bawolff (talk) 22:00, 10 March 2026 (UTC)

@Bawolff: ah, I thought it was the other way around! (Shows what tools I don't use.) - Jmabel ! talk 05:30, 11 March 2026 (UTC)

I can get a list with Quarry - can VFC perform an update using a manual list? I don't think EXIF shows up in VFC's search query. But looking deeper into VFC at Help:VisualFileChange.js/samples#Inserting variables, there seem to be examples of pulling information EXIF out and duplicating it elsewhere - seems like this might work, will look into it further. I've never worked with bots and would prefer to do this on my own if possible. -Consigned (talk) 10:11, 11 March 2026 (UTC)

In case its helpful: https://quarry.wmcloud.org/query/103004 Bawolff (talk) 18:05, 11 March 2026 (UTC)

Thanks, this is indeed helpful. I'm still stuck with VFC not being able to use a custom list of files and its criteria not able to access EXIF, but am going to look into AWB. -Consigned (talk) 10:21, 17 March 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. --廣九直通車 (talk) 05:47, 9 April 2026 (UTC)

Croptool won't let me overwrite

Hello, I was trying to crop this image, and I decided to overwrite instead of uploading new (which I haven't tried before), but I got this text: "Upload failed! [api] Received error: abusefilter-disallowed : ⧼abusefilter-warning-file-overwriting⧽". I would have assumed it would let me, considering I'm Autoconfirmed, so I'm allowed to do most other actions. Does this require a higher level of permission? LetmeEditit (talk) 19:15, 10 March 2026 (UTC)

@LetmeEditit Yes, you need autopatrol to overwrite files. Please see COM:OVERWRITE. You may request an exception for that specific file, or you can request the autopatrol permission. Thanks. Tvpuppy (talk) 19:45, 10 March 2026 (UTC)

You would need "Autopatrol" for that, see Commons:Overwriting existing files. Please request that right on COM:RFR#Autopatrol, with your 4k edits, it should be a no-brainer to get it. If you don't want to wait for it, ping me, I'll add {{Allow Overwriting}} for a short time. Regards, Grand-Duc (talk) 19:46, 10 March 2026 (UTC)

Thank you both for informing me. I've put in a request for autopatrol now. I probably won't use it much, since most of the time I think uploading a separate file is better, but it seems like a nice thing to have the option. Side note — I think the error message should be changed to be more clear, it's very vague. LetmeEditit (talk) 20:02, 10 March 2026 (UTC)

@LetmeEditit: but how could it be appropriate to crop in place a file that is used in articles in multiple Wikipedias, rather than upload your own version? You are forcing a change on every one of those Wikipedias. Have you properly read COM:OVERWRITE? - Jmabel ! talk 05:32, 11 March 2026 (UTC)

COM:OVERWRITE is kind of confusing, and it seems like a lot of the policy on here should really be re-written for more clarity. I personally feel like a crop to the image fits the example provided at Commons:Overwriting existing files#Substantial crop or un-crop, since the grass is a fairly repetitive negative space, which IMO doesn't add any value to the image. The image's use case in each article is to illustrate the unique colour of the fox, and I think the large section of grass detracts from that, as it makes the fox hard to see.

I think the best solution would be to re-write this section of policy, as a new user it's confusing and seems contradictory in places. LetmeEditit (talk) 12:13, 11 March 2026 (UTC)

Pinging @Tvpuppy, Grand-Duc, since you both apparently see no problem here. What am I missing? - Jmabel ! talk 05:34, 11 March 2026 (UTC)

You're right, in this case, a new file should be created instead of overwriting. Admittedly, I didn't pay much attention to the file, as I was focused on answering the part about permission to overwrite. Thanks for your additional comment above. Tvpuppy (talk) 10:28, 11 March 2026 (UTC)

I feel a comradeship in spirit with Tvpuppy here... I also only thought about the technological prerequisites of overwriting, not so much about whether the actual act would be sensible here. When I looked at the fox image, I thought, "Yeah, there's lot of background, a crop to the main motif is not a bad idea", but failed to notice the pages where it's used. Regards, Grand-Duc (talk) 11:00, 11 March 2026 (UTC)

Request for privacy: Change Author field to "Unknown" on my uploads

Hello,

For privacy and safety reasons, I would like to request a batch update for all files uploaded by my account (formerly Risantana or "Cheposo", now Stratos 499).

I need the |Author= field in the {{Information}} template of all my previous uploads to be changed from "Risantana" to "Unknown" or "Anonymous". My goal is to ensure that my current or former username is no longer linked to these files' metadata or description fields.

Could a bot operator or an administrator assist me with this mass edit?

Thank you for your understanding and help regarding this privacy matter.

Regards, --Stratos 449 (talk) 13:36, 11 March 2026 (UTC)

@Stratos 449: Hi, Works created by you, and uploaded under a free license, cannot be credited to "Unknown". However you can choose whatever pseudonym you want. Yann (talk) 17:07, 11 March 2026 (UTC)

They could relicense it to a different license that does not require attribution. Bawolff (talk) 20:41, 14 March 2026 (UTC)

Including you can use your current account name, if that will do. - Jmabel ! talk 21:18, 11 March 2026 (UTC)

Creating a WD item from Artwork information

Hi, Please see Template talk:Artwork#Creating a WD item from Artwork information. Yann (talk) 18:15, 11 March 2026 (UTC)

Overwrite files per OpenRefine

Hi!

Deutsch: Ich habe mehrere Dateien über OpenRefine hochgeladen. Mir ist aufgefallen, dass ein URL-Parameter TIFF-Dateien hochgeladen hochgeladen hat, die keine eingebetteten Koordinaten hatten. Die Lösung besteht darin, die neuen URLs zu nutzen und auf die Dateinamen zu überschreiben. Dies funktioniert auch soweit (OpenRefine gibt den Hinweis aus, dass die Datei überschrieben wird), aber die eigentliche Überschreibung erfolgt nicht. Der Mimetype ist derselbe, und ein manuelles Überschreiben via URL funktioniert ohne Meckern. Die Dateien unter neuem Namen hochzuladen und die alten zu löschen, möchte ich vermeiden. Für Ratschläge bin ich dankbar :3.

English: I uploaded several files via OpenRefine. I noticed that a URL parameter uploaded TIFF files that did not have embedded coordinates. The solution is to use the new URLs and overwrite the files to their respective file names. This works so far (OpenRefine displays a message that the file is being overwritten), but the actual overwrite does not take place. The MIME type is the same, and manual overwriting via URL works without any problems. I would like to avoid uploading the files under new names and deleting the old ones. I am grateful for any advice :3.

--PantheraLeo1359531 😺 (talk) 09:01, 13 March 2026 (UTC)

Might help if you would indicate at least one of the files in question, and if the file page does not name the relevant URL(s), please be explicit about that too. - Jmabel ! talk 18:41, 13 March 2026 (UTC)

Of course, sorry! We have File:DOP20 RGB Berlin Sommer 2025 - 373000 5808000 (Senatskanzlei Berlin).tif from TIF source. I would overwrite this file per OpenRefine from the URL GeoTIFF source. --PantheraLeo1359531 😺 (talk) 13:35, 14 March 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. --廣九直通車 (talk) 05:47, 9 April 2026 (UTC)

Tech News: 2026-12

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• The Improved Syntax Highlighting beta feature, also known as CodeMirror 6, has been used for wikitext syntax highlighting since November 2024. It will be promoted out of beta by May 2026 in order to bring improvements and new features to all editors who use the standard syntax highlighter. If you have any questions or concerns about promoting the feature out of beta, please share. [1]
• Some changes to local user groups are performed by stewards on Meta-Wiki and logged there only. Now, interwiki rights changes will be logged both on Meta-Wiki and the wiki of the target user to make it easier to access a full record of user's rights changes on a local wiki. Past log entries for such changes will be backfilled in the coming weeks. [2]
• On wikis using Flagged Revisions, the number of pending changes shown on Special:PendingChanges previously counted pages which were no longer pending review, because they have been removed from the system without being reviewed, e.g. due to being deleted, moved to a different namespace, or due to wiki configuration changes. The count will be correct now. On some wikis the number shown will be much smaller than before. There should be no change to the list of pages itself. [3]
• Wikifunctions composition language has been rewritten, resulting in a new version of the language. This change aims to increase service stability by reducing the orchestrator's memory consumption. This rewrite also enables substantial latency reduction, code simplification, and better abstractions, which will open the door to later feature additions. Read more about the changes.
• Users can now sort search results alphabetically by page title. The update gives an additional option to finding pages more easily and quickly. Previously, results could be sorted by Edit date, Creation date, or Relevance. To use the new option, open 'Advanced Search' on the search results page and select 'Alphabetically' under 'Sorting Order'. [4]
• View all 28 community-submitted tasks that were resolved last week. For example, the bug that prevented UploadWizard on Wikimedia Commons from importing files from Flickr has now been fixed. [5]

Updates for technical contributors

• A new special page, Special:LintTemplateErrors, has been created to list transcluded pages that are flagged as containing lint errors to help users discover them easily. The list is sorted by the number of transclusions with errors. For example: Special:LintTemplateErrors/night-mode-unaware-background-color. [6]
• Users of the Improved Syntax Highlighting beta feature have been using CodeMirror instead of CodeEditor for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages, for some time now. Along with promoting CodeMirror 6 out of beta, the plan is to replace CodeEditor as the standard editor for these content models by May 2026. Feedback or concerns are welcome. [7]
• The CodeMirror JavaScript modules will soon be upgraded to CodeMirror 6. Leading up to the upgrade, loading the ext.CodeMirror or ext.CodeMirror.lib modules from gadgets and user scripts was deprecated in July 2025. The use of the ext.CodeMirror.switch hook was also deprecated in March 2025. Contributors can now make their scripts or gadgets compatible with CodeMirror 6. See the migration guide for more information. [8]
• The MediaWiki Interfaces team is expanding coverage of REST API module definitions to include extension APIs. REST API modules are groups of related endpoints that can be independently managed and versioned. Modules now exist for GrowthExperiments and Wikifunctions APIs. As we migrate extension APIs to this structure, documentation will move out of the main MediaWiki OpenAPI spec and REST Sandbox view, and will instead be accessible via module-specific options in the dropdown on the REST Sandbox (i.e., Special:RestSandbox, available on all wiki projects).
• The Scribunto extension provides different pieces of information about the wiki where the module is being used via the mw.site library. Starting last week, the library also provides a way of accessing the wiki ID that can be used to facilitate cross-wiki module maintenance. [9]
• Detailed code updates later this week: MediaWiki

In depth

• The 2026 Coolest Tool Award celebrating outstanding community tools, is now open for nominations! Nominate your favorite tool using the nomination survey form by 23 March 2026. For more information on privacy and data handling, please see the survey privacy statement.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 19:33, 16 March 2026 (UTC)

Opera browser data saver mode

this probably niche problem happened to me today. writing here in case anyone might have it too.

i couldnt edit using opera browser on my android phone. after some testing i realised that my ip is different (according to whatismyipaddress.com) when i use chrome and opera. turning off data saver finally makes ip the same and lets me be no longer affected by ip blocks. RoyZuo (talk) 20:22, 17 March 2026 (UTC)

simpleSVGcheck.js is defect

Tracked in Phabricator
Task T420626

The script User talk:Chealer/simpleSVGcheck.js doesn't work anymore. @Flexagoon wrote:

The script no longer works for me, because requests to the validator API are blocked by Content-Security-Policy

— in: User_talk:Chealer/simpleSVGcheck.js#Blocked_by_CSP

What can we do to fix this? Kind regards, --Sebastian Wallroth (talk) 12:38, 19 March 2026 (UTC)

@Sebastian Wallroth (and others): Please do file a subtask of phab:T419265 for any CSP issues in userscripts/gadgets that have started happening -- my comment here (on metawiki) has links to some partially-prefilled task templates I put together in case they're helpful, though it's not required to use them! Best, ‍—‍a smart kitten_[meow] 14:09, 19 March 2026 (UTC)

Thanks! I created a report and added @Sebastian Wallroth as a subscriber. Flexagoon (talk) 18:22, 19 March 2026 (UTC)

Images seem to be broken

I'm into computer programming, and I've heard that wikimedia commons recently archived most of their images, but now none of them show up on my webpages. I don't know how to input images into my HTML code anymore.

here is a link that doesn't work.

https://upload.wikimedia.org/wikipedia/commons/thumb/9/92/Snowy_Mountain_Valley.jpg/1599px-Snowy_Mountain_Valley.jpg

pretty much all of the old images are broken like this, and they simply don't show up on my webpages. Dragonstudios36 (talk) 14:52, 20 March 2026 (UTC)

Use https://upload.wikimedia.org/wikipedia/commons/thumb/9/92/Snowy_Mountain_Valley.jpg/1920px-Snowy_Mountain_Valley.jpg instead. Try using one of the sizes from this list: 20px, 40px, 60px, 120px, 250px, 330px, 500px, 960px, 1280px, 1920px, 3840px [Personally I find it really silly we are just breaking everything instead of just using redirects]. Near the top of the image page there should be a button labelled "use this file" which will give you html code to include the file. Bawolff (talk) 19:24, 20 March 2026 (UTC)

Rewriting the RotateLink gadget

So, I'm rewriting the RotateLink gadget.. The current UI is pretty old - no dark theme, image preview sometimes doesn't load, and the interface isn't very user-friendly. I'm thinking about putting a slider at the bottom of the file preview while keeping the preview centered. Here's what I'm designing now: imgur (direct video: [10]). Open to suggestions; I've been reading some comments on MediaWiki talk:Gadget-RotateLink.js. Nemoralis (talk) 23:43, 21 March 2026 (UTC)

 Comment, the new UI looks very nice, thanks for creating it. Just a minor suggestion, can you specify in the gadget text that the rotation is "clockwise"? I know it is quite obvious, but I think it's better to be clear. Thanks. Tvpuppy (talk) 11:36, 22 March 2026 (UTC)

@Tvpuppy, thanks, I added it. New UI is now live: MediaWiki talk:Gadget-RotateLink.js#Rewrite. Nemoralis (talk) 18:27, 22 March 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. --廣九直通車 (talk) 05:47, 9 April 2026 (UTC)

Tech News: 2026-13

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• Wikimedia site users can now log in without a password using passkeys. This is a secure method supported by fingerprint, facial recognition, or PIN. With this change, all users who opt for passwordless login will find it easier, faster, and more secure to log in to their accounts using any device. The new passkey login option currently appears as an autofill suggestion in the username field. An additional "Log in with passkey" button will soon be available for users who have already registered a passkey. This update will improve security and user experience. The screen recording demonstrates the passwordless login process step by step.
• All wikis will be read-only for a few minutes on Wednesday, 25 March 2026 at 15:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.

Updates for editors

• Wikimedia site users can now export their notifications older than 5 years using a new Toolforge tool. This will ensure that users retain their important notifications and avoid them being lost based on the planned change to delete notifications older than 5 years, as previously announced. [11]
• Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to Special:PersonalDashboard. This is an early version of an experience that introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project. [12]
• The Special:Block now has two minor interface changes. Administrators can now easily perform indefinite blocks through a dedicated radio button in the expiry section. Also, choosing an indefinite expiry provides a different set of common reasons to select from, which can be changed at: MediaWiki:Ipbreason-indef-dropdown. [13]
• Mobile editors at several wikis can now see an improved logged-out edit warning, thanks to the recent updates from the Growth team. These changes released last week are part of ongoing efforts and tests to enhance account creation experience on mobile and then increase participation. [14]
• View all 36 community-submitted tasks that were resolved last week. For example, the bug that prevented mobile web users from seeing the block information when affected by multiple blocks has been fixed. They can now see messages of all the blocks currently affecting them when they access Wikipedia.

Updates for technical contributors

• Images built using Toolforge will soon get the upgraded buildpacks version, bringing support for newer language versions and other upstream improvements and fixes. If you use Toolforge Build Service, review the recent cloud-announce email and update your build configuration as necessary to ensure your tools are compatible. [15][16]

• The API Portal documentation wiki will shut down in June 2026. API keys created on the API Portal will continue to work normally. api.wikimedia.org endpoints will be deprecated gradually starting in July 2026. Documentation on the API Portal is moving to mediawiki.org. Learn more on the project page.
• Detailed code updates later this week: MediaWiki

In depth

• WMDE Technical Wishes is considering improvements to automatically generated reference names in VisualEditor. Please check out the proposed solutions and participate in the request for comment.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 16:48, 23 March 2026 (UTC)

• Can someone give a better explanation of the thing about notifications? I don't understand whether this is specific to notifications still on the user talk page or, if not, how it would affect already-archived talk pages. - Jmabel ! talk 20:07, 23 March 2026 (UTC)

  Don't know what you mean. Notifications are the thing that display in the dropdown in the top right. Info on the technical system it uses, Echo, can be found at mw:Extension:Echo. Apparently they want to delete notifications older than 5 years. Prototyperspective (talk) 22:44, 23 March 2026 (UTC)

  • Ah, so this is presumably about notifications one has long since dealt with. Got it. I knew those were called notifications, but presumed it had to be something else, because who on earth looks at a notification more than a few days, maybe a month, after the fact? Five years?? (I guess someone cares...). - Jmabel ! talk 00:44, 24 March 2026 (UTC)

Annotations invisible for logged out users

Per title - COM:Image annotations are not displayed unless you are logged in. Qbli2mHd (talk) 01:11, 25 March 2026 (UTC)

Well that makes sense because only logged in users can use gadgets. Nemoralis (talk) 18:39, 25 March 2026 (UTC)

Hmm, it is actually loaded for all users via Common.js. It works for me in a private window (logged out). Nemoralis (talk) 18:47, 25 March 2026 (UTC)

I think I understand where this comes from - annotations won't work if page width (determined on load) leads to image being resized. This happens when the window is too narrow to fit an image; annotations will work if you reload the page with a wider window; they won't work again if you make the window even wider, because a sidebar is inserted to the right and image is resized; they will work again if you make window wide enough to fit both the image and the sidebar. Qbli2mHd (talk) 17:47, 26 March 2026 (UTC)

Placeholder images

MOVED from COM:Help desk - Jmabel ! talk 05:37, 25 March 2026 (UTC)
On some image pages this placeholder image : https://commons.wikimedia.org/w/resources/assets/file-type-icons/fileicon-ogg.png is being incorrectly inserted into the html under the "use this file" link. example here: https://commons.wikimedia.org/wiki/File:Ravenscar_-_geograph.org.uk_-_401270.jpg Ndurgom (talk) 09:46, 24 March 2026 (UTC)
END MOVED - Jmabel ! talk 05:37, 25 March 2026 (UTC)

@Ndurgom: I've moved your question to this page where it is more likely to be addressed. - Jmabel ! talk 05:37, 25 March 2026 (UTC)

I don't see a "Use this file" link. Is it the one included by Help:Gadget-Stockphoto? I don't have that enabled. MKFI (talk) 18:35, 25 March 2026 (UTC)

@MKFI: It is.

ANOTHERWlKlPEDlAN _{wɑit thɑt’s ɑ typo} 23:24, 25 March 2026 (UTC)

Its probably because the resolution is so low there are no "view in other resolution" links. User:Krinkle recently made a bunch of fixes to the gadget and i think one of them was to use those other resolution links to pick the download size. [Im guessing here, have not really looked into it]. Bawolff (talk) 09:08, 27 March 2026 (UTC)

Tracked in Phabricator
Task T421557

@Ndurgom @Bawolff I filed T421557 and am implementing a workaround in the gadget. Krinkle (talk) 23:01, 27 March 2026 (UTC)

Hi, this looked to be fixed but I just found a couple more examples of the fileicon-ogg.png appearing in the embed code of the "Use this file" option:

https://commons.wikimedia.org/wiki/File:Dale_House,_Chapel-le-Dale_-_geograph.org.uk_-_2499193.jpg

https://commons.wikimedia.org/wiki/File:Ingleborough_summit_area_-_geograph.org.uk_-_3593674.jpg Ndurgom (talk) 17:43, 9 April 2026 (UTC)

State of Flickr2Commons?

Flickr2Commons is not working for me right now. I can work around it, but does anyone know what is going on? - Jmabel ! talk 20:02, 27 March 2026 (UTC)

Same issues at April 8. 2026 6D (talk) 05:22, 8 April 2026 (UTC)

More precisely: everything seems normal along the way, but the actual upload never completes. - Jmabel ! talk 06:21, 28 March 2026 (UTC)

Need help for MassRename

Deutsch: Nachdem ich mehrere Dateien hochgeladen hatte, habe ich gemerkt, dass ich durch einen Vorlagenfehler falsche Koordinaten in den Dateinamen gelegt habe. Glücklicherweise konnte ich die eigentlich korrekten Dateinamen rekonstruieren, und habe sie in eine CSV-Datei gelegt Link zur Cloud auf Filen. Kann jemand mit einem Bot die Dateien umbenennen, sodass die Dateinamen passen? Das wäre echt klasse. Herzlichen Dank!

English: After uploading several files, I realized that due to a template error, I had included incorrect coordinates in the filenames. Fortunately, I was able to reconstruct the correct filenames and saved them in a CSV file Link to Filen cloud. Can someone use a bot to rename the files so that the filenames match? That would be really great! Thank you a lot!

--PantheraLeo1359531 😺 (talk) 20:30, 28 March 2026 (UTC)

In der Datei liegen Datensätze in der folgenden Form vor: „https://gdi.berlin.de/services/wms/truedop_2020_sommer?service=WMS&version=1.3.0&REQUEST=GetMap&LAYERS=truedop_2020_sommer_rgb&CRS=EPSG:25833&WIDTH=5000&HEIGHT=5000&FORMAT=image/geotiff&STYLES=&BBOX=396000,5816000,397000,5817000;DOP20 RGB Berlin 2020 - 397000 5828000 (Senatskanzlei Berlin).tif;DOP20 RGB Berlin 2020 - 396000 5816000 (Senatskanzlei Berlin).tif;DOP20RGB Berlin 2020 (Senatskanzlei Berlin)“ . Für einen Bot wäre folgende Angabe besser geeignet: „ 'DOP20 RGB Berlin 2020 - 397000 5828000 (Senatskanzlei Berlin).tif';'DOP20 RGB Berlin 2020 - 396000 5816000 (Senatskanzlei Berlin).tif' “ . Nur der alte und der gewünschte Dateiname in einer Zeile. GeorgDerReisende (talk) 20:56, 28 March 2026 (UTC)

 Done So, jetzt sind nur noch die Namen vorhanden :) --PantheraLeo1359531 😺 (talk) 21:05, 28 March 2026 (UTC)

Es braucht einen neuen öffentliche Link. GeorgDerReisende (talk) 21:25, 28 March 2026 (UTC)

Ah entschuldige, ich dachte, der alte Link bleibt aktiv. Damit sollte es klappen. --PantheraLeo1359531 😺 (talk) 21:51, 28 March 2026 (UTC)

In der vorliegenden Reihenfolge dürfen die Dateien nicht verschoben werden! Sonst würden verschiedene Dateien mehrfach überschrieben werden und damit viele Dateien verloren gehen. Nur als Beispiel: in einmal soll „370000 5808000“ auf „370000 5810000“ verschoben werden, dann soll „370000 5810000“ auf „370000 5814000“ verschoben werden, dann „370000 5814000“ auf „371000 5812000“! Usw. Außerdem heißt es auf der Dateibeschreibung, dass es sich um Quadrate von 2x2 km handeln soll, die Koordinaten verweisen aber auf 1x1 km-Quadrate. Ich würde das gerne überprüfen, kann das aber erst am Dienstag machen. GeorgDerReisende (talk) 22:18, 29 March 2026 (UTC)

Du hast Recht! Ich kann das aufklären :). Die erwähnten 2×2km sind der Blattschnitt, die die Senatskanzlei vorgibt. Da die Bilder über den Web Map Service bezogen wurden (und nicht bereits gekachelt), habe ich den Zuschnitt aller Kacheln auf 1km×1km begrenzt, um die Konsistenz über alle Jahre hinweg zu gewährleisten (wenn ich also ein Koordinatenpaar in der Suche eingebe, bekomme ich für jedes Jahr denselben Ausschnitt) (leider gibt es einige Inkonsistenzen über die Jahre, die ich versucht habe, zu überwinden). Es ist richtig, dass einige Namen bereits "belegt" sind. Kann man da vielleicht die betreffenden Dateien zu Namen verschieben, die einen "temporären Platzhalter" im Namen haben, sodass dann die richtigen Namen frei werden? Danke und liebe Grüße! --PantheraLeo1359531 😺 (talk) 16:15, 30 March 2026 (UTC)

@GeorgDerReisende (Ping) --PantheraLeo1359531 😺 (talk) 16:15, 30 March 2026 (UTC)

(Die Originalbeschreibungen wurden pro Forma übernommen. Es kann bei einigen Fällen gekachelte Downloads geben, die allerdings im JP2-Format vorliegen und verlustfrei komprimiert sein können) --PantheraLeo1359531 😺 (talk) 16:17, 30 March 2026 (UTC)

1. In der Dateiverschiebungsliste sind die Dateien der Serie „RGB Berlin 2021“ doppelt vorhanden, wenn noch auf Basis dieser Liste gearbeitet werden soll, muss die zweite Erwähnung der Serie (ab Zeile 6001) gelöscht werden.

2. Die Dateien mit den Koordinaten 368000/5808000, 368000/5809000, 369000/5808000, 369000/5809000, 370000/5806000, 370000/5807000, 371000/5814000, 371000/5815000, 372000/5804000, 372000/5805000, 373000/5828000, 373000/5829000, 374000/5806000, 374000/5807000, 375000/5828000, 375000/5829000, 376000/5806000, 376000/5807000, 377000/5830000, 377000/5831000, 378000/5806000, 378000/5807000, 379000/5832000, 379000/5833000, 380000/5806000, 380000/5807000, 381000/5832000, 381000/5833000, 382000/5806000, 382000/5807000, 383000/5836000, 383000/5837000, 384000/5806000, 384000/5807000, 385000/5836000, 385000/5837000, 386000/5806000, 386000/5807000, 387000/5834000, 387000/5835000, 388000/5804000, 388000/5805000, 390000/5806000, 390000/5807000, 392000/5810000, 392000/5811000, 394000/5826000 und 394000/5827000 brauchen nicht bearbeitet zu werden, da sie laut Liste nicht verschoben werden sollen.

3. Ich finde den Fehler nicht, der zu dieser Situation geführt hat.

3a. Lösung 1 — die dreckige Methode: du lädst einfach alle Dateien mit dem richtigen Namen nochmal über die Dateien mit dem falschen Namen hoch. Ergebnis: für jede Datei werden 37 MB Speicherplatz zusätzlich benötigt und in der Versionsgeschichte taucht die falsche Dateiversion mit auf, was in der Zukunft Probleme mit sich bringen könnte.

3b. Lösung 2 — die saubere Methode: du beantragst die Löschung dieser 7200 Dateien und sie wird so durchgeführt und dann lädst du die Dateien mit den richtigen Namen erneut hoch. Ergebnis: für jede Datei werden nur die 37 MB einmalig benötigt und es gibt eine saubere Versionsgeschichte. Nachteil: ein Dateilöscher-Admin muss die 7200 Dateien einzeln händisch löschen, offenbar gibt es für solche Massenlöschungen keinen Bot.

3c. Lösung 3 — die extrem arbeitsintensive Lösung: wie von mir schon anfangs beschrieben, gibt es Ketten von notwendigen Dateiverschiebungen. Diese Ketten musst du alle identifizieren. Dann kann mit einem Bot so gearbeitet werden: move( Datei987 nach DateiTemp ), move( Datei765 nach Datei987 ), move( Datei444 nach Datei765 ), move( DateiTemp nach Datei444 ). Usf.

Ich für mich würde die Lösung 2 vorschlagen und dem Dateilöscher-Admin eine Palette Gummibären oder so zukommen lassen. GeorgDerReisende (talk) 13:46, 31 March 2026 (UTC)

Alles klar, ich würde dann die Tage ggf. die Löschung der betroffenen Dateien beantragen und die Dateien mit korrektem Namen neu hochladen. Danke Dir für Deinen Einsatz! --PantheraLeo1359531 😺 (talk) 08:43, 2 April 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. --廣九直通車 (talk) 05:48, 9 April 2026 (UTC)

Misfunction of "license reviewed failed, all right reserveds" on several pages.

Hello, MediaWiki:Gadget-LicenseReview.js cannot function properly when using license review failed, then select "All rights reserved" as the rational. For example, on this page, File:Angelica Bove Funweek.it 2024.jpg
This is a screenshot of a copyrighted video from youtube. Lemonaka (talk) 00:59, 30 March 2026 (UTC)

Tech News: 2026-14

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• The Beta version of Abstract Wikipedia a new Wikimedia project which is language-independent, was launched last week. The project allows communities to build Wikipedia articles in their native language, which can be readily accessed by other users in their own languages. The wiki is powered by instructions from Wikifunctions and also based on structured content from Wikidata. Read more.

Updates for editors

• The Growth team is running an A/B test to evaluate a clearer, more user-friendly message that promotes account creation on wikis. Currently when logged-out mobile users begin editing, they see a jarring warning message that can feel abrupt and discouraging. This also presents temporary account editing as the default rather than encouraging account creation. The test is running on ten Wikipedias, including Arabic, French, Spanish and German. Read more.
• The Wikimedia Apps team is inviting feedback on how editing should work on the Wikipedia mobile apps. The discussion focuses on improving how users access editing tools when they tap "Edit". This is part of a broader effort to convert readers who develop an interest in editing, to access a more user-friendly pathway to start contributing.
• View all 45 community-submitted tasks that were resolved last week. For example, an issue where citation fetching from the large newspaper archive Newspapers.com was no longer working, due to a block in Citoid requests, has now been fixed. [17]

Updates for technical contributors

• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 19:22, 30 March 2026 (UTC)

Did anyone else see this?

I went to Category:Tavares, Florida and on the {{Wikidata Infobox}} instance there I saw that the "official website" link read "Official Website of [somebody's name that started with I, think the second name started with H]". The link was correct and refreshing the page made it return to just "official website". Did anyone else see this or am I just losing my mind (small loss)? - The Bushranger (talk) 19:34, 1 April 2026 (UTC)

Bug with Notices

Noticed (heh) this evening that the 'Notices' tab on Commons is not allowing you to clear notices from other Wikimedia projects unless you clear it from that project. - The Bushranger (talk) 01:36, 2 April 2026 (UTC)

Ah that's great news since I recently accidentally clicked on one of these multi-notification items from another project (one from Commons while on English Wikipedia). Looks like I didn't lose my notifications then. I think this bug is good to have as a safeguard but it would be much better if there was a setting to require confirmation if one marks multiple or even all notifications as read (and then the issue you described was fixed). See wish W472: Confirmation dialog to prevent accidental clicks on Mark All As Read for notifications in the ongoing Community Wishlist. Prototyperspective (talk) 13:37, 2 April 2026 (UTC)

Database servers in cluster31 are overloaded

I noticed today that when I try to access my watchlist page here in Commons from Edge (but the same problem also appears in Chrome - I see cluster26 mentioned there) an error message appears.

Sorry! This site is experiencing technical difficulties.

Try waiting a few minutes and refreshing.

(Cannot access the database: Cannot access the database: Database servers in cluster31 are overloaded. In order to protect application servers, the circuit breaking to databases of this section have been activated. Please try again a few seconds.)

The problem doesn't go away with waiting and refreshing, and can also appear when accessing Commons from the wikishootme tool. C messier (talk) 12:29, 2 April 2026 (UTC)

Installing and testing my own user scripts

I am trying to get acquainted with user scripts here on Commons. As a first exercise, I would like to create a script based on MediaWiki:Gadget-QInominator.js. Since I don't want to tamper with the actual gadget, I have created a new script in my namespace (User:Aciarium/test260402.js). However, I seemingly was not able to install it, despite trying to follow the instructions on en:Wikipedia:User_scripts#How_do_you_install_user_scripts? and Commons:User scripts. Is there something I am missing here? I would expect that after installation (and bypassing the browser cache), I could go on any page of a file I uploaded and see the "Nominate this image for QI" option there, known from the original gadget. How can I actually install and test my script? --Aciarium ⚒ (talk) 15:10, 2 April 2026 (UTC)

@Aciarium, do you see any errors on the browser console? Nemoralis (talk) 21:43, 3 April 2026 (UTC)

@Nemoralis Nevermind, I tried installing my script one more time with the browser console open, and adding the mw.loader.load command to my common.js file actually did the trick. Thanks however! --Aciarium ⚒ (talk) 20:01, 4 April 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. --廣九直通車 (talk) 05:48, 9 April 2026 (UTC)

Help to convert and upload 3 videos

Hi, I want to migrate these three videos to Commons, but both of the programs I use to convert .mp4 to webm are having trouble with them. Can someone help?

https://catalog.archives.gov/id/18004

https://catalog.archives.gov/id/16008

https://catalog.archives.gov/id/16277

Thank you! Victorgrigas (talk) 18:23, 2 April 2026 (UTC)

@Victorgrigas: you don't say what tools you have tried and failed with. Have you used https://video2commons.toolforge.org/? - Jmabel ! talk 19:57, 2 April 2026 (UTC)

Hi! I am using Miro Video Converter and Movavi Video Converter 7 (cause it's non-subscription), I'll try video2commons, i gave up on it years ago cause it fails for youtube now but I realize now that you mention it that it can be used for uploading a file directly. Thanks. Victorgrigas (talk) 23:10, 2 April 2026 (UTC)

@Victorgrigas: You may also find the VLC media player useful, it can re-encode stuff (including videos), is able to digest virtually all media formats that exist and is free and open source. Regards, Grand-Duc (talk) 00:20, 3 April 2026 (UTC)

@Victorgrigas you can do that using com:v2c like i just did File:The Grand Duchess of Luxembourg thanks the US, Luxembourg ; Civilians surrender arms, etc, Stendal, Germany.webm for https://catalog.archives.gov/id/18004 .

click "download", copy the mp4 link ( https://s3.amazonaws.com/NARAprodstorage/lz/mopix/111/adc/111-adc-4202.mp4 for 18004 that i already did), paste it in v2c, and proceed to upload. RoyZuo (talk) 10:52, 7 April 2026 (UTC)

Action Required: Update templates/modules for electoral maps (Migrating from P1846 to P14226)

Hello everyone,

This is a notice regarding an ongoing data migration on Wikidata that may affect your election-related templates and Lua modules (such as Module:Itemgroup/list).

The Change:
Currently, many templates pull electoral maps from Wikidata using the property distribution map (P1846), combined with the qualifier depicts (P180): electoral result (Q19571328).

We are migrating this data (across roughly 4,000 items) to a newly created, dedicated property: apportionment diagram (P14226).

What You Need To Do:
To ensure your templates and infoboxes do not break or lose their maps, please update your local code to fetch data from P14226 instead of the old P1846 + P180 structure. A list of pages was generated using Wikimedia Global Search.

Deadline:
We are temporarily retaining the old data on P1846 to allow for a smooth transition. However, to complete the data cleanup on Wikidata, the old P1846 statements will be removed after May 1, 2026. Please update your modules and templates before this date to prevent any disruption to your wiki's election articles.

Let us know if you have any questions or need assistance with the query logic. Thank you for your help! ZI Jony using MediaWiki message delivery (talk) 17:09, 3 April 2026 (UTC)

Can SVGedit.js fix the image below?

• 
  The file I'm referring to.

When I open on Inkscape, it opens normally and the full image is shown, but when it's displayed on Wikipedia, part of the image doesn't show. If it's solved midway, disconsider. Candidyeoman55 (talk) 18:28, 3 April 2026 (UTC)

@Candidyeoman55: questions like this are usually better asked at Commons:Graphic Lab/Illustration workshop. - Jmabel ! talk 22:59, 3 April 2026 (UTC)

But how can I use the SVGedit.js to try to fix this file? Candidyeoman55 (talk) 23:15, 3 April 2026 (UTC)

I have no idea and, as I said above, this is not a particularly good place to ask. - Jmabel ! talk 03:49, 4 April 2026 (UTC)

Administrators' rename tool has problem maybe.

See below. Please check the top line of the Summary.

• Old revision of File:Tea plantation in Peermade - panoramio.jpg
• Old revision of File:Tea plantations in Periyar - panoramio (2).jpg
• Old revision of File:Valara Waterfalls (4).jpg
• Old revision of File:Mattupetty Dam (1).jpg
• Old revision of File:State Highway 43 in Thankamany.jpg
• Old revision of File:Tea estate in Meghamalai.jpg

Voncercue (talk) 02:18, 5 April 2026 (UTC)

• I assume you are talking about Special:Diff/1190534914, Special:Diff/1146338126, etc. Looks like it matches a string incorrectly, having a string end with the first instance of "}}" without looking for the possibility of balanced "{{"/"}} pairs within the string. Sadly, you can't do truly proper balancing of brackets with a regex (it has no stack), and I don't think our regex implementation has recursion (or some equivalent) to do this. Still, it ought to be possible to deal with some finite level of nesting. - Jmabel ! talk 16:58, 5 April 2026 (UTC)

• Thank you. I now understand when this happens. I will fix it manually. Also, I changed the link to the file above to Template:Oldid. --Voncercue (talk) 23:56, 5 April 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. --廣九直通車 (talk) 05:48, 9 April 2026 (UTC)

After marking notices as "read" they keep coming back as unread

Tracked in Phabricator
Task T422218

Is anyone else getting this problem? Starting a day or 2 ago, when I mark new notices as read, they reappear within moments as unread. My list of supposedly unread notices just keeps getting longer and longer. -- WikiPedant (talk) 03:25, 5 April 2026 (UTC)

Ah, I see this issue was raised a couple days ago by User:The Bushranger. But going back to each of the many wikis I edit to clear notices is not terribly convenient. -- WikiPedant (talk) 03:32, 5 April 2026 (UTC)

@WikiPedant, hello! You can Ctrl+Click on each notice and it would mark them as "read"; it's fast. Deltaspace42 (talk) 22:28, 6 April 2026 (UTC)

@Deltaspace42: Many thanks! -- WikiPedant (talk) 03:57, 7 April 2026 (UTC)

phab:T422218. Nemoralis (talk) 11:09, 6 April 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. --廣九直通車 (talk) 05:49, 9 April 2026 (UTC)

Page spaces in which to search

While people are reporting little glitches: Search here on Commons keeps losing my favored list of page spaces in which to search. Each time this happens I restore it without any great difficulty, but why would this keep getting lost? - Jmabel ! talk 17:00, 5 April 2026 (UTC)

Tech News: 2026-15

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

• The CampaignEvents extension now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in the documentation.
• The new watchlist labels feature (announced in Tech News 2026-07) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via EditWatchlist. In all three places it is a new field following the expiry field.
• View all 23 community-submitted tasks that were resolved last week. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed. [18]

Updates for technical contributors

• The sub-referencing feature, which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to more wikis later this year. Wikis using the Reference Tooltips gadget are encouraged to update their version (typically at MediaWiki:Gadget-ReferenceTooltips.js as shown here) to ensure compatibility. Other reference-related gadgets may also be affected. [19]
• All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions. Read more.
• The Action API has had several formats for requested output. One of them, format=php, is being removed soon. Please ensure your scripts or bots use the JSON format. This removal should affect very few scripts and bots. [20]
• The Special:NamespaceInfo page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia. [21]
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 16:16, 6 April 2026 (UTC)

[Bug] Commons:Meet our photographers

Good evening everyone.

When viewing this page from a smartphone: [22], not all photographers appear. ComputerHotline (talk) 11:36, 7 April 2026 (UTC)

Persistent 0x0 image size error for PDF files

Tracked in Phabricator
Task T420341

Dear all technical users, Commons (as well as all other projects using files from Commons) has experienced a persistent 0x0 image size error for PDF files. In short, the system fails to generate thumbnails of pages for certain PDF files (typically larger ones). This has seriously affected works on Wikisource, where "Failed to initialize OpenSeadragon, no image found." is displayed on affected pages. OCR is also disabled.

While Yann reported that purging and uploading dummy files (then reverting to the old file) sometimes work, it is not effective for other cases. He also mentions that the problem worsens in the few days. While a Phabricator report is created, it has stalled for many weeks.

Comments from experienced users are appreciated, and follow-up measures on Phabricator are even more appreciated, thank you.廣九直通車 (talk) 11:45, 8 April 2026 (UTC)

Image size issue

I just noticed that, apparently, on images, the links for "880 x 522 pixels" and "640 x 441 pixels" versions of images actually both link to the same size image ("960px-[imagename stuff]"). This can't be intentional, can it? The Bushranger (talk) 16:04, 9 April 2026 (UTC)

@The Bushranger: since not all files are going to have the same aspect ratios, can you link to a file that is an example of what you are talking about? - Jmabel ! talk 20:16, 9 April 2026 (UTC)

I do see something like this at File:En route from Mila 23 to Letea - 27 - water lilies.jpg: 640 × 427 pixels leads to "960...", 1,024 × 683 pixels and 1,280 × 853 pixels both lead to "1280...", "2,560 × 1,707" leads to "3840...". - Jmabel ! talk 20:21, 9 April 2026 (UTC)

@Jmabel: , heres two: File:Vickers Valiant B.2 4Sep53.png ("680 x 360" and "800 x 450" both lead to "960...") and File:Vulcan at Manston - Flickr - Elsie esq..jpg ("640 x 441" and "800 x 552" both link to "960..."). - The Bushranger (talk) 20:26, 9 April 2026 (UTC)

@Jmabel@The Bushranger The software only renders a fixed set of common sizes to reduce server loads - see mw:Common thumbnail sizes. Any usage of images loads one of these sizes and scales it in-page to the desired size. That's a change from a few months ago IIRC. It is somewhat frustrating that most of the default sizes listed on file pages don't match those sizes, so (as you experienced) the links are rather misleading. Pi.1415926535 (talk) 21:34, 9 April 2026 (UTC)

In short, the left hand does not know what the right hand is doing.

Do we have any control over what sizes are offered on file pages, or do we have to wait for one set of WMF engineers to finally notice what another set of WMF engineers are doing? (If the latter, a phabricator report might speed this up.) - Jmabel ! talk 22:06, 9 April 2026 (UTC)

This is a known issue, but it's one of those where we were mostly waiting for the dust to settle on the other changes wrt to file sizing before dealing with it. —TheDJ (talk • contribs) 07:39, 10 April 2026 (UTC)