• Skip to content
  • Skip to primary sidebar
  • Skip to footer

Foliovision

Main navigation

  • Weblog
    • FV Player
    • WordPress
    • Video of the Week
    • Case Studies
    • Business
  • About
    • Testimonials
    • Meet the Team
    • We Support
    • Careers
    • Contact
    • Pricing
  • Products
  • Support
    • FV Player Docs
    • Pro Support
  • Login
  • Basket is empty
Affordable VAST/VPAID for Wordpress has arrived. Serve ads with your videos starting today!

How to publish full size images in WordPress

22 November 2021 / Alec Kinnear / Leave a Comment

Since WordPress 5.3, WordPress by default prevents publishers from sharing images wider or taller than 2560px. This is a nuisance if you want to share full sized-images.

Why does WordPress prevent publishers from sharing full-size images by default

The reason the limitation is there is that there are many mobile phones which take photos up to 48MP. A single photo measures 8000×6000 pixels and clocks in at 15 MP as a jpeg. Serving up images in this format will make mobile phone visitors very unhappy and will earn publishers a big penalty in Google Page Speed scores. So WordPress decided to play big brother here and prevent publishers from penalising themselves with visitors and Google.

What’s important to note is that if any publishers believe that by serving and linking only 2560px images, they are protected from copyright thieves, they are not protected.

If you upload a 5000px file, after WordPress 5.3 it will show up as 2560px wide by default.

Here’s what the URL will look like:

https://uncoy.com/images/2021/11/20211107-124523-Aurelien-back-from-tasting-dirt-scaled.jpg

That’s great, except it’s very easy for someone who wants the original to simply remove -scaled from the end.

https://uncoy.com/images/2021/11/20211107-124523-Aurelien-back-from-tasting-dirt.jpg

This will get you the full size image.

It’s important to only upload the largest file which you’d like to share with the world to your WordPress website.

That said, there’s a good chance that some publishers do want to share at least 4K images with their audience. There’s lots of visitors out there with UHD monitors (also known as 4K) at 3840 x 2160px. For instance with my football pictures, I like to share 4K images for those browing them at home. Many of the images are large scale shots conceived for viewing in detail.

For instance, this image is called Two Trainers. The subject is not the players (who are out of focus) but about both coaches and both team benches watching the game in front of them at the same time:

Zoltan Fekete and Erwin Raithofer watch fast action in front of the team benches

The subject extends across the width of the full image. It’s better to let people see the full 7251 × 2910 pixels image. This is not the best example but just one which came up in the first football post on Uncoy.com. There are times where it is much better to give people the larger immage.

How to disable WordPress 2560px image size limit via theme or via functions.php

In this case, there are two choices to disable the default nanny function which limits image size to 2560px. Unfortunately there’s no GUI for this, so one has the choice of modifying one’s theme with this code:

add_filter( 'big_image_size_threshold', '__return_false' );

I don’t like theme based modifications as if one changes the theme, all kinds of unexpected trouble results. Here’s the code you should add to functions.php:

function td_big_image_size_threshold( $threshold, $imagesize, $file, $attachment_id ) {
    return 4096;
}
add_filter( 'big_image_size_threshold', 'td_big_image_size_threshold', 10, 4 );

We will also be adding have added a preference to the images options screen (~/wp-admin/options-media.php) via our BusinessPress WordPress missing features plugin.

Planned Improvements to WordPress image settings in BusinessPress.

Here’s what the new screen looks like:

There’s a very decent plugin by Jonathan Desrosiers called Disable Big Image Threshold but we try to avoid adding a whole plugin to manage a single very small issue like this.

Steps to take before uploading very large images to WordPress

Don’t leave compression up to WordPress or even a third-party add-on service like Ewww, ShortPixel or WP Compress as it slows down publishing and often won’t correct your original. My final step before publishing a set of large images is to run them through the free ImageOptimize before uploading.

Here’s my settings:

I choose 90% as that creates much smaller files with almost no visual loss. It’s important to leave quality very high as WordPress will be resizing from these sub-masters.

ImageOptimize routinely takes my 20 MB masters and turns them into 2 MB highly optimized but full sized jpegs.

Alec Kinnear

Alec Kinnear

Alec has been helping businesses succeed online since 2000. Alec is an SEM expert with a background in advertising, as a former Head of Television for Grey Moscow and Senior Television Producer for Bates, Saatchi and Saatchi Russia.

Categories: WordPress Tags: images, publishing, WordPress

Related Posts

  1. How to restore missing WordPress Featured Image Screen Option

  2. Lightbox For Full Size Images

    Lightbox For Full Size Images

  3. WordPress images uploaded by client too large? try Imsanity

    WordPress images uploaded by client too large? try Imsanity

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

You can click here to Subscribe without commenting

Primary Sidebar

Categories

  • Business
  • Camera Reviews
  • Case Studies
  • Design
  • FV Player
  • Internet Marketing
  • IT
  • Life
  • SEO
  • Slovak
  • Video of the Week
  • WordPress

Footer

Our Plugins

  • FV WordPress Flowplayer
  • FV Thoughtful Comments
  • FV Simpler SEO
  • FV Antispam
  • FV Gravatar Cache
  • FV Testimonials

Free Tools

  • Pandoc Online
  • Article spinner
  • WordPress Password Finder
  • Delete LinkedIn Account
  • Responsive Design Calculator
Foliovision logo
All materials © 2025 Foliovision s.r.o. | Panská 12 - 81101 Bratislava - Slovakia | info@foliovision.com
  • This Site Uses Cookies
  • Privacy Policy
  • Terms of Service
  • Site Map
  • Contact
  • Tel. ‭+421 2/5292 0086‬

We are using cookies to give you the best experience on our website.

You can find out more about which cookies we are using or switch them off in .

Powered by  GDPR Cookie Compliance
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Necessary Cookies

Strictly Necessary Cookie allow you to log in and download your software or post to forums.

We use the WordPress login cookie and the session cookie.

If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.

Support Cookies

Foliovision.com uses self-hosted Rocket.chat and self-hosted Freescout support desk to provide support for FV Player users. These cookies allow our visitors to chat with us and/or submit support tickets.

We are delighted to recommend self-hosted Rocket.chat and especially Freescout to other privacy-conscious independent publishers who would prefer to self-host support.

Please enable Strictly Necessary Cookies first so that we can save your preferences!

3rd Party Cookies

This website uses Google Analytics and Statcounter to collect anonymous information such as the number of visitors to the site, and the most popular pages.

Keeping this cookie enabled helps us to improve our website.

We reluctantly use Google Analytics as it helps us to test FV Player against popular Google Analytics features. Feel free to turn off these cookies if they make you feel uncomfortable.

Statcounter is an independent Irish stats service which we have been using since the beginning of recorded time, sixteen years ago.

Please enable Strictly Necessary Cookies first so that we can save your preferences!