Compose Preview Screenshot Testing

Screenshot testing is an effective way to verify how your UI looks to users. The Compose Preview Screenshot Testing tool combines the simplicity and features of composable previews with the productivity gains of running host-side screenshot tests. Compose Preview Screenshot Testing is designed to be as easy to use as composable previews.

A screenshot test is an automated test that takes a screenshot of a piece of UI and then compares it against a previously approved reference image. If the images don't match, the test fails and produces an HTML report to help you compare and find the differences.

With the Compose Preview Screenshot Testing tool, you can:

  • Identify a number of existing or new composable previews you want to use for screenshot tests.
  • Generate reference images from those composable previews.
  • Generate an HTML report that identifies changes to those previews after you make code changes.
  • Use @Preview parameters, such as uiMode or fontScale, and multi-previews to help you scale your tests.
  • Modularize your tests with the new screenshotTest source set.
Figure 1. Example HTML report.


To use Compose Preview Screenshot Testing, you need the following:

  • Android Gradle 8.5.0-beta01 or higher.
  • Kotlin 1.9.20 or higher.


To enable the tool, follow these steps:

  1. Add the plugin, version 0.0.1-alpha01 to your project.
    1. Add the plugin to your version catalogs file:
      agp = "8.5.0-beta01"
      kotlin = "1.9.20"
      screenshot = "0.0.1-alpha01"
      screenshot = { id = "", version.ref = "screenshot"}
    2. In your module-level build.gradle.kts file, add the plugin in the plugins {} block:
      plugins {
  2. Enable the experimental property in your project's file.
  3. In the android {} block of your module-level build.gradle.kts file, enable the experimental flag to use the screenshotTest source set and ensure that kotlinCompilerExtensionVersion is set to 1.5.4 or higher.
    android {
        composeOptions {
            kotlinCompilerExtensionVersion = "1.5.4"
        experimentalProperties["android.experimental.enableScreenshotTest"] = true
  4. Make sure you've added the ui-tooling dependency.
    1. Add it to your version catalogs:
      androidx-compose-ui-tooling = { group = "androidx.compose.ui", name = "ui-tooling"}
    2. Add it to your module-level build.gradle.kts file:
      dependencies {

Designate composable previews to use for screenshot tests

To designate the composable previews you want to use for screenshot tests, place the previews in a test class. The test class file must be located in the new screenshotTest source set, for example app/src/screenshotTest/kotlin/com/google/yourapp/ExamplePreviewScreenshots.kt ({module}/src/screenshotTest/{kotlin|java}/com/your/package).

You can add more composables and/or previews, including multi-previews, in this file or other files created in the same sourceset.


import androidx.compose.runtime.Composable
import androidx.compose.ui.tooling.preview.Preview

class ExamplePreviewsScreenshots {

    @Preview(showBackground = true)
    fun GreetingPreview() {
        MyApplicationTheme {

Generate reference images

After you set up a test class, you need to generate reference images for each preview. These reference images are used to identify changes later, after you make code changes. To generate reference images for your composable preview screenshot tests, run the following Gradle task:

  • Linux and macOS: ./gradlew updateDebugScreenshotTest (./gradlew {:module:}update{Variant}ScreenshotTest)
  • Windows: gradlew updateDebugScreenshotTest (gradlew {:module:}update{Variant}ScreenshotTest)

After the task completes, find the reference images in app/src/debug/screenshotTest/reference ({module}/src/{variant}/screenshotTest/reference).

Generate a test report

Once the reference images exist, run the validate task to take a new screenshot and compare it with the reference image:

  • Linux and macOS: ./gradlew validateDebugScreenshotTest (./gradlew {:module:}validate{Variant}ScreenshotTest)
  • Windows: gradlew validateDebugScreenshotTest (gradlew {:module:}validate{Variant}ScreenshotTest)

The verification task creates an HTML report at {module}/build/reports/screenshotTest/preview/{variant}/index.html.

Known issues

You can find the current list of known issues in the tool's Issue Tracker component. Report any other feedback and issues through the issue tracker.