Toolkit.getDefaultToolkit().createImage() vs ImageIO.read()

Question

I'm creating a UI using Swing and I want to display an image in a JLabel. The code I use is the following:

 JLabel label = new JLabel(new ImageIcon(ImageIO.read(new File("img.jpg"))));

This works fine if I use png images but when it comes to jpg (only some of them), I get a redish image (a different one than the one I see in Paint.NET). The image I used is this one: img.jpg

So I tried (as an alternative):

Toolkit.getDefaultToolkit().createImage(new File("img.jpg").getAbsolutePath());

Does anyone have an idea of why this happening? Is it a special JPEG format which is not supported?
I've read on this forum that most people recommend to use ImageIO (here for example). Why?

Thanks a lot

Yes it does. That's why I wonder why people recommend the other way ... — , Aug 20 '12 at 16:36
Wait, I can't find any `createImage(File f)` in the Toolkit Java docs...sure? — Volker Stolz, Aug 20 '12 at 16:48
Sorry I'm using `createImage(String path)`, I edited the question... — , Aug 20 '12 at 16:56

score 8 · Accepted Answer · edited May 23 '17 at 10:10

8

As discussed here, your JPEG image may contain spurious transparency information. One simple expedient is to render the image in a buffer having a compatible color model, as shown here.

edited May 23 '17 at 10:10

Community

1
1

answered Aug 20 '12 at 18:32

trashgod

203,806
29
246
1,045

1

See also [`createCompatibleImage()`](http://docs.oracle.com/javase/6/docs/api/java/awt/GraphicsConfiguration.html). – trashgod Aug 20 '12 at 18:46

lbalazscs · Answer 2 · 2012-08-20T18:13:19.987

It looks like you have found a bug in ImageIO.read... (I can reproduce the red tint, and it is definitely not how it should look like).

You can try to

save the JPEG files with other settings
open/re-save the file with other programs (hoping to get a more common JPEG-encoding)
or use the Toolkit method (if you don't control the images).

The only problem with the Toolkit method is that the getImage() method returns immediately after it is invoked and the loading is happening on a background thread, so you cannot start working with the Image object immediately.

Toolkit.getDefaultToolkit().createImage() vs ImageIO.read()

2 Answers2

Linked