Why I/we pixel peep - Quality Gives Options

A debate on Twitter earlier in the week (see below) put up one of THE most frequently asked questions about phone imaging. Why do I/we both pixel peeping when most phone-shot photos are only ever seen on 5"/6" phone screens? It's a good question, but I think I have a great answer. If you're a phone imaging enthusiast then you'll know where I'm going with this already, but for the casual user, here's why I do what I do and here's why enthusiasts care...

The question's often phrased in comments here, of course. But it reared up again after people watched MKBHD's latest phone camera comparison shootout. It was unashamedly looking at photos when compared on Instagram and Twitter, with polls for each and millions, repeat millions of votes were cast. With crazy results, such as the latest iPhone cameras being defeated in 'round 1', with the top-notch Google Pixel cameras going much the same way, and with mid-range phone cameras such as that on the Blackberry Key2 and Pocofone F1 almost managing to topple the Huawei Mate 20 Pro, a flagship I've largely dismissed for its heavy handed image processing. But it fits in well with the other results from this low resolution test.

You see, as MKBHD explains in the video, after the fact, people mainly voted on exposure and contrast, as expressed by these Twitter and Instagram (low resolution) expressions, and attributes like detail and purity were left in the rear view mirror.

Now, prompting this very article, @NiceChapHere on Twitter posted:

But most people see such photos on social media. They go through compression and lose detail. I can't think of a common case where one would view the full image on their desktop these days.

It's a fair point - if all anyone saw of phone-shot photos were phone-sized/social-hosted renderings then almost any phone camera from about 2014 onwards will fit the bill for most shots (extremes of low light excepted). "Good enough for Facebook" has been a cliche for the last decade and it's still true. A phone camera can be low end and with artfacts and glitches galore, yet when viewed in a 600-pixel wide Facebook or Twitter post it'll look just fine.

In fact, such low grade images often look better than 'high quality' photos at such low resolutions or on phone screens, because they're artificially sharpened and edge enhanced, to try and overcome the limitations of their sensors. Which is understandable, even if the end result of asking the general public which photos are 'better' ends up being counter-intuitive.

But, of course, there are genuine real world reasons why phone cameras needs to be better, and why I need to 'pixel peep' (i.e. look at 1:1 crops) in order to diffentiate the 'good' from the 'best':

  1. Processing. The more natural, the more detailed, a starting image is, the more can be done to it later (e.g. in Snapseed, Adobe Elements, Lumia Creative Studio, or similar). In contrast, if you take the typical mid-range, sharpened, enhanced photo that impresses so much on social media, and try to do anything else to it, you'll quickly hit ugliness and you'll lose even more detail. 'Garbage in, garbage out', and so on. 
     
    Now, I'm the first to admit to loving to tweak my phone-shot images. A straighten here, a crop there, a little more saturation, and then 'heal' out that telephone wire. That sort of thing. But you can only do all this to create stunning results if the starting image hasn't had too much done to it in the first place. In my tests, the Lumias, iPhones and Pixels do well in this regard, while Samsung, Huawei and other phone flagships tend to overdo the pixel-level sharpening and edge enhancement, and lower cost phones even more so, and this all limits what can be done later.
     
  2. Cropping later. Several of my favourite people shots, framed in the family house, are of faces taken from a 'group' shot. You know the drill - "Hey, Debbie looks great in that one!" or "Joe's really cute there, shame about the rest of your ugly mugs!" Or perhaps it's as simple as a landscape shot of a scene which is nice enough, but you love a particular section of the frame - maybe a house or boat or whatever. If your original 9MP image (say) was of low quality then even though it looks fine at 'social' resolution, once you crop down to 25% (i.e. a quarter of the original frame) then all you'll see are blocky artefacts and ugly edges. Whereas if the original was of high enough quality then there will be genuine detail to still admire, even at (here) around 2MP.
     
  3. Noise and low light. Low light is what 'sorts the men from the boys', as it were. Shoot in dim conditions with a low or mid-range phone camera and you'll get a gloomy, noisy mess. Do the same on a really good phone camera (e.g. Lumia 950, Pixel 3) and you'll have loads of OIS, PureView and multi-frame noise-cancellation tech lending a hand, giving a clear and useable photo. When I pixel peep, I'm looking for noise and artefacts in anything other than perfect sunny conditions. And these will only get worse as the light reduces, of course.

A simulated example will help, I'm sure, using images A and B:

Note that the interactive comparator below uses javascript and does need to load each pair of images. Please be patient while this page loads, if you see a pair of images above each other than you've either not waited long enough or your browser isn't capable enough! You ideally need a powerful, large-screened tablet or a proper laptop or desktop. This comparator may not work in some browsers. Sorry about that. On Windows 10 Mobile, use the 'AAWP Universal' UWP app, which handles the comparator very competently (see the tips in the app's help screens).

A nice shot of a group of people in good light. One taken with current smartphone flagship quality at 8MP and one taken with a current low-to-mid-range phone camera, also at '8MP'. Which one do you prefer, A or B? Just wait to make sure the page has fully loaded and then use your mouse or trackpad pointer to compare the images:

A B

What's interesting here is that I bet many people would pick B as slightly 'better'. At worst, there would be an even split between opinions. Which just goes to show how much you shouldn't trust web/screen-sized photos as indicators of image quality. Because A is the quality photo and B is the low-grade version. Just because a photo looks sharp at 900 pixels (here) doesn't mean it's any good for anything else - post processing or cropping. 

By way of illustration, let's take the smiling black lady on the right. "Hey", she says, "I love this shot, can you crop this for me, I want to frame it for my husband". OK, so you dive into Paint or similar on these two 8MP images, and then crop to just the lady. I've labelled the crops this time, partly because it's obvious which is which:

Again, wait to make sure the page has fully loaded and then use your mouse or trackpad pointer to compare the images:

From HQ 8MP original From low-grade 8MP original

A dramatic difference - the higher quality 8MP original has been able to stand cropping down like this and still delivers a useable - even printable and frameable - photo, while the lower quality 8MP shot (typically from a £150 phone) produces something that's unsatisfying, to say the least.

So that's why I pixel peep - because until you do so, you don't really see whether a phone camera is delivering real image quality and not just something that wows on the phone screen but disappoints once you really take a look or need to work on the photo some more.

Comments and data points welcome...

Published by Steve Litchfield at 7:45 UTC, December 6th

Section: Articles
Categories: How To, Comment, Hardware
Platforms: General, Symbian^3, General, Windows Phone 8