Documentation versions (currently viewingVaadin 8)

Vaadin 8 reached End of Life on February 21, 2022. Discover how to make your Vaadin 8 app futureproof →

Embedded Resources

You can embed images in Vaadin UIs with the Image component, Adobe Flash graphics with Flash, and other web content with BrowserFrame. There is also a generic Embedded component for embedding other object types. The embedded content is referenced as resources, as described in "Images and Other Resources".

The following example displays an image as a class resource loaded with the class loader:

Image image = new Image("Yes, logo:",
    new ClassResource("vaadin-logo.png"));

The caption can be given as null to disable it. An empty string displays an empty caption which takes a bit space. The caption is managed by the containing layout.

You can set an alternative text for an embedded resource with setAlternateText(), which can be shown if images are disabled in the browser for some reason. The text can be used for accessibility purposes, such as for text-to-speech generation.

Embedded Image

The Image component allows embedding an image resource in a Vaadin UI.

// Serve the image from the theme
Resource res = new ThemeResource("img/myimage.png");

// Display the image without caption
Image image = new Image(null, res);

The Image component has by default undefined size in both directions, so it will automatically fit the size of the embedded image. If you want scrolling with scroll bars, you can put the image inside a Panel that has a defined size to enable scrolling, as described in "Scrolling the Panel Content". You can also put it inside some other component container and set the overflow: auto CSS property for the container element in a theme to enable automatic scrollbars.

Generating and Reloading Images

You can also generate the image content dynamically using a StreamResource, as described in "Stream Resources", or with a RequestHandler.

If the image changes, the browser needs to reload it. Simply updating the stream resource is not enough. Because of how caching is handled in some browsers, you can cause a reload easiest by renaming the filename of the resource with a unique name, such as one including a timestamp. You should set cache time to zero with setCacheTime() for the resource object when you create it.

// Create the stream resource with some initial filename
StreamResource imageResource =
    new StreamResource(imageSource, "initial-filename.png");

// Instruct browser not to cache the image

// Display the image
Image image = new Image(null, imageResource);

When refreshing, you also need to call markAsDirty() for the Image object.

// This needs to be done, but is not sufficient

// Generate a filename with a timestamp
SimpleDateFormat df = new SimpleDateFormat("yyyyMMddHHmmssSSS");
String filename = "myfilename-" + df.format(new Date()) + ".png";

// Replace the filename in the resource


The BrowserFrame allows embedding web content inside an HTML <iframe> element. You can refer to an external URL with ExternalResource.

As the BrowserFrame has undefined size by default, it is critical that you define a meaningful size for it, either fixed or relative.

BrowserFrame browser = new BrowserFrame("Browser",
    new ExternalResource(""));

Notice that web pages can prevent embedding them in an <iframe>.

Generic Embedded Objects

The generic Embedded component allows embedding all sorts of objects, such as SVG graphics, Java applets, and PDF documents, in addition to the images, and browser frames which you can embed with the specialized components.

Display an SVG image:

// A resource reference to some object
Resource res = new ThemeResource("img/reindeer.svg");

// Display the object
Embedded object = new Embedded("My SVG", res);
object.setMimeType("image/svg+xml"); // Unnecessary

The MIME type of the objects is usually detected automatically from the filename extension with the FileTypeResolver utility in Framework. If not, you can set it explicitly with setMimeType(), as was done in the example above (where it was actually unnecessary).

Some embeddable object types may require special support in the browser. You should make sure that there is a proper fallback mechanism if the browser does not support the embedded type.