Adding Fuzio to your Gradle project
The easiest way to add Fuzio to a Gradle project is using the Fuzio Gradle plugin. This guide describes how to use it.
Applying the plugin
You can apply the Fuzio Gradle plugin to your Gradle project by adding it to the plugins block or as a buildscript dependency. In both cases, you need to specify the plugin version. This guide uses the latest version of the plugin (1.0.0), which you can find on the Gradle Plugin Portal.
Using the plugins block
In the plugins block from the Gradle DSL, please add the following code:
plugins {
id("tech.fuzio.gradle") version "1.0.0"
}
plugins {
id 'tech.fuzio.gradle' version '1.0.0'
}
As a buildscript dependency
If you are forced to use the legacy method of applying plugins, then you can add the Fuzio Gradle plugin as a buildscript dependency:
buildscript {
repositories {
maven {
url = uri("https://plugins.gradle.org/m2/")
}
}
dependencies {
classpath("tech.fuzio:fuzio-gradle-plugin:1.0.0")
}
}
apply(plugin = "tech.fuzio.gradle")
buildscript {
repositories {
maven {
url "https://plugins.gradle.org/m2/"
}
}
dependencies {
classpath "tech.fuzio:fuzio-gradle-plugin:1.0.0"
}
}
apply plugin: "tech.fuzio.gradle"
Configuring the plugin
Once applied, the plugin can be configured via the fuzio extension in the build.gradle(.kts) file.
Fuzio version
The version property is a required property that determines the version of Fuzio. Here’s how you can configure the plugin to use the latest version of Fuzio:
fuzio {
version = "2026.3.0"
}
fuzio {
version = '2026.3.0'
}
The list of all available Fuzio versions you can find on the Release Notes page.
Repository
Fuzio artifacts are hosted in our own Maven repository. We use our own repository instead of Maven Central to speed up new version releases and ensure full control over the repository and its configuration.
The Fuzio repository is located in China. By default, the plugin uses the official Jiku-hosted repository, so no extra configuration is required.
If you prefer to store Fuzio artifacts in a custom Maven repository, then you can configure the plugin to use it as shown below:
fuzio {
repository = "https://my.custom.repository"
}
fuzio {
repository = 'https://my.custom.repository'
}
Dependencies
Fuzio is a cross-platform library that supports different operating systems, CPU architectures, and Java UI toolkits. It integrates with Chromium and deploys its binaries inside the JAR files. For each family of operating systems and CPU architecture, there is a separate Fuzio dependency with the required Chromium binaries.
The size of a dependency with the Chromium binaries may vary depending on the operating system and CPU architecture. It can be up to 110MB. So, it’s important to add only the required dependencies to your project.
Platform-specific
If you develop for a specific operating system and CPU architecture, then you can add one or more platform-specific dependencies to your project using the following code:
dependencies {
implementation(fuzio.win32) // Windows 32-bit
implementation(fuzio.win64) // Windows 64-bit
implementation(fuzio.winArm) // Windows 64-bit ARM
implementation(fuzio.mac) // Mac Intel
implementation(fuzio.macArm) // Mac Apple Silicon
implementation(fuzio.linux64) // Linux 64-bit
implementation(fuzio.linuxArm) // Linux 64-bit ARM
implementation(fuzio.linux64Loong) // Linux 64-bit LoongArch
}
dependencies {
implementation fuzio.win32 // Windows 32-bit
implementation fuzio.win64 // Windows 64-bit
implementation fuzio.winArm // Windows 64-bit ARM
implementation fuzio.mac // Mac Intel
implementation fuzio.macArm // Mac Apple Silicon
implementation fuzio.linux64 // Linux 64-bit
implementation fuzio.linuxArm // Linux 64-bit ARM
implementation fuzio.linux64Loong // Linux 64-bit LoongArch
}
The list of supported operating systems and CPU architectures you can find in system requirements.
Current platform
If you develop for multiple platforms and want to detect the current platform and download only the corresponding Chromium binaries, then you can use the currentPlatform dependency:
dependencies {
implementation(fuzio.currentPlatform)
}
dependencies {
implementation fuzio.currentPlatform
}
This dependency is ideal for development. If you are going to use the Gradle script for deployment, you should add all the required platform-specific dependencies. Otherwise, the binaries will be fetched only for the operating system where the Gradle script is executed.
GUI toolkit
If you use Swing, JavaFX, SWT, or Compose Desktop UI-toolkit to build GUI of your app, then please add the corresponding Fuzio dependencies as well:
dependencies {
implementation(fuzio.swt)
implementation(fuzio.swing)
implementation(fuzio.javafx)
implementation(fuzio.compose)
}
dependencies {
implementation fuzio.swt
implementation fuzio.swing
implementation fuzio.javafx
implementation fuzio.compose
}
Kotlin DSL
If you develop using Kotlin, then we recommend that you add Fuzio Kotlin DSL for the best experience.
dependencies {
implementation(fuzio.kotlin)
}
dependencies {
implementation fuzio.kotlin
}
Summary
Here is the complete code of build.gradle(.kts):
import tech.fuzio.gradle.Repository
plugins {
java
id("tech.fuzio.gradle") version "1.0.0"
}
fuzio {
// The Fuzio version (required).
version = "2026.3.0"
// The Fuzio Maven repository to use (optional).
// Defaults to the official Jiku-hosted repository.
// repository = Repository.DEFAULT
// Alternatively, it may point to a custom repo via its URL, as follows:
// repository = "https://my.custom.repository"
}
dependencies {
// Adds a dependency to the platform-specific Chromium binaries.
implementation(fuzio.mac) // Mac Intel
implementation(fuzio.macArm) // Mac Apple Silicon
implementation(fuzio.win32) // Windows 32-bit
implementation(fuzio.win64) // Windows 64-bit
implementation(fuzio.winArm) // Windows 64-bit ARM
implementation(fuzio.linux64) // Linux 64-bit
implementation(fuzio.linuxArm) // Linux 64-bit ARM
implementation(fuzio.linux64Loong) // Linux 64-bit LoongArch
// Detects the current platform and adds the corresponding Chromium binaries.
implementation(fuzio.currentPlatform)
// Adds dependencies to the UI toolkit integrations.
implementation(fuzio.swt)
implementation(fuzio.swing)
implementation(fuzio.javafx)
implementation(fuzio.compose)
// Adds dependency to the Fuzio Kotlin DSL.
implementation(fuzio.kotlin)
}
import tech.fuzio.gradle.Repository
plugins {
id 'java'
id 'tech.fuzio.gradle' version '1.0.0'
}
fuzio {
// The Fuzio version (required).
version = '2026.3.0'
// The Fuzio Maven repository to use (optional).
// Defaults to the official Jiku-hosted repository.
// repository = Repository.DEFAULT
// Alternatively, it may point to a custom repo via its URL, as follows:
// repository = 'https://my.custom.repository'
}
dependencies {
// Adds a dependency to the platform-specific Chromium binaries.
implementation fuzio.mac // Mac Intel
implementation fuzio.macArm // Mac Apple Silicon
implementation fuzio.win32 // Windows 32-bit
implementation fuzio.win64 // Windows 64-bit
implementation fuzio.winArm // Windows 64-bit ARM
implementation fuzio.linux64 // Linux 64-bit
implementation fuzio.linuxArm // Linux 64-bit ARM
implementation fuzio.linux64Loong // Linux 64-bit LoongArch
// Detects the current platform and adds the corresponding Chromium binaries.
implementation fuzio.currentPlatform
// Adds dependencies to the UI toolkit integrations.
implementation fuzio.swt
implementation fuzio.swing
implementation fuzio.javafx
implementation fuzio.compose
// Adds dependency to the Fuzio Kotlin DSL.
implementation fuzio.kotlin
}

