The source image is very fuzzy and poorly focused itself. This has nothing to do with the image rendering of the browser. Your screenshot matches what the photo quality of the site is.

okay.. this is a low quality image. i am updating it.

image viewing behavior in current beta (58) changed a lot. in previous beta (57) and current stable(56), it looks like there is a lot of boxes in image (as you can see in screenshot)

http://cdn.wallpapersafari.com/80/27/VnN650.jpg

this is a better image.

Steps to reproduce the problem:
1. open the link in chrome  stable or beta or dev (image will not view clearly)
2. long click on image
3. click "download image"
4. after downloaded, there will be an option "open" at bottom
5. click on open (image will not view clearly)
6. from 3 dot menu choose "open with" (any image viewer on mobile)
7. now, image looks pretty

What is the expected behavior?
chrome should behave like default browser.

screenshot of chrome stable, dev and default browser (Android 4.2.2).
cdn.wallpapersafari.com/80/27/VnN650.jpg

Deleted: Screenshot_2017-03-20-13-45-48.png 164 KB

	Screenshot_2017-03-20-13-45-48.png 164 KB View Download

Deleted: Screenshot_2017-03-20-13-46-13.png 117 KB

	Screenshot_2017-03-20-13-46-13.png 117 KB View Download

Deleted: Screenshot_2017-03-20-13-49-09.png 238 KB

	Screenshot_2017-03-20-13-49-09.png 238 KB View Download

I've opened all of those images in stable, canary and dev channels on android and they all look the same.

Do you have Data Saver enabled in one of the browsers but not the others?

no, I haven't enabled data saving none of them. did you test them on Android 4.2.2? I have noticed 58 has some improvement on page viewing (pages are plain). here is github login page.

Deleted: stable.png 41.0 KB

	stable.png 41.0 KB View Download

Deleted: canary.png 37.6 KB

	canary.png 37.6 KB View Download

Thank you for providing more feedback. Adding requester "schenney@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The testers tried Android 4.2.2. Could you clear browsing data to ensure this is not a cache issue.

And I do not understand the Comment #7. Is it directly related to this issue?

I have actually reinstall from play store. so, no cache problem. step 5 of comment 3 should not affected by cache or data saving (I think).

I am noticing these problem for long (57 and lower). by comment 7, I mean that, in 56, webpages also look like lot of boxes (just like images. please see navigation bar of that). but it is fixed now.

I don't know why the result defers on your site.

is it somehow related to this https://upload.wikimedia.org/wikipedia/commons/9/9a/Colour_banding_example01.png ?

Thank you for providing more feedback. Adding requester "schenney@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I'm not sure what we can do about this. It appears to be a decoding issue but, since we can't reproduce it, it probably is related to the specific graphics hardware on your phone. Nowhere do I see which phone model you are using. Please provide that.

it is Bangladeshi branded mobile. may be, it is possible to reproduce the problem on mediatek mt6572 mobile.
 
symphony w68 (also known as viettel V8508, intex cloud y2 in other country)
GPU: Mali 400 
SoC: mediatek mt6572

Thank you for providing more feedback. Adding requester "schenney@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I fixed the issue today on 56 by using chrome://flags/#enable-gpu-rasterization
"force enabled for all layers" ;). now webpages and images(almost) behave like default browser.

Will I leave this issue as closed and open separate issue for comment 4 & 7 for 58?

(forgot to mention on previous comment "comment 7 > sign in button")

Closing due to inactivity, please reopen if needed.