How to install Liberica Native Image Kit on Windows PC

This guide will help you to install Liberica native image kit on Windows PC. Liberica NIK is a multilingual tool based on GraalVM that transforms your applications into performant native images. Go to bell-sw.com. Open the downloads menu and select download libera native image kit. You will arrive on the downloads page. The builds of Liberica NIK up to version 23 are distributed in a manner different from newer versions. We will show you how to install both types of packages.

Liberica NIK up to version 23 is available in three packages. Core package contains all you need for Java development. Standard version includes dependencies for non-java programming languages. Full version also includes Liberica FX for open JFX development. Liberica NIK 24 and higher is available in two packages for Java development. JDK standard version contains all you need for Java development. JDK full version also includes Liberica FX for Open JFX development. To download builds of Liberica NIK for apps written in other programming languages, you need to get the package dedicated to the programming language of your choice. Each one is available as nativebased and Java based.

Let's use Liberica NIK 24 standard and NodeJS package as examples and install them on Windows 10. Download the installation file and run it. Click next. You'll be presented with the following options. Add to path will add the installation folder to the path environment variable which will allow you to run the files from that folder without switching to it. Setup Java home will create a Java home variable and set it to the location of Liberica NIK. This will make Liberica NIK a default Java runtime. Associate JAR files option will make Liberica NIK a default utility when you open jar files. We recommend selecting all three options. Click next. Click install. When the installation is complete, click finish. Let's test if the installation was successful. Open the command prompt and type native-image. As you can see, the application ran without issues.

Now, let's set up the NodeJS Java standalone liber. Extract the archive into any folder. Go to your Windows settings. Select system about advanced system settings. Click the environment variables button. Here you need to set up variables for your standalone package. As you can see, the Java home path is already set as Liberica NIK installation folder. Find the path variable in user variables if you want to set up for current user only or system variables if you set up for all users. Click the path variable and edit button. Click the new button and add the path to the bin folder of your standalone package. Click OK two times and close the settings. Let's test it. Open the command prompt and type node. It should run. Don't forget that Liberica NIK requires Microsoft Visual Studio 2017 with Microsoft Visual C++ 15 or later.

Summary

This guide explains how to install Liberica Native Image Kit (NIK) on a Windows PC. Liberica NIK, based on GraalVM, converts applications into efficient native executables. Builds up to version 23 come in three packages (Core, Standard, Full), while version 24+ offers two Java development packages (Standard and Full). To install, download the installer from bell-sw.com, run it, and select options to set up PATH, JAVA_HOME, and associate JAR files. After installation, test by running native-image in Command Prompt. For standalone language packages (e.g., Node.js), extract the archive, update system PATH, and confirm the setup. Note: Microsoft Visual Studio 2017+ with C++ 15+ is required.

Videos
card image
Aug 6, 2025
GraalVM for Java Developers: The Ultimate Beginner’s Guide

What is GraalVM and how can it improve your Java applications? In just 10 minutes, this video explains the three main components of GraalVM — the JIT compiler, Native Image, and Polyglot API. Learn how to boost performance, reduce startup time, and combine multiple languages in one app. Whether you’re building microservices, serverless apps, or just exploring modern JVM tooling, this is your quick-start guide to GraalVM.

Videos
card image
Jul 15, 2025
Java Downgrade Challenge: From JDK 8 to 1.1 (Part 2)

In Part 2 of the Java Downgrade Challenge, we continue our journey — now from Java 8 all the way to Java 1.1. No streams, no lambdas, no generics, no collections — and at one point, we even boot up Windows 98. If you thought Part 1 was painful, this one unwinds Java history line by line. By the end, the familiar Java from today will be almost gone.

Further watching

Videos
card image
Aug 27, 2025
Buildpacks for Spring Boot

Buildpacks for Spring Boot: no Dockerfiles, no hassle — just production-ready container images in one command. Tired of maintaining Dockerfiles? In this tutorial, you’ll learn how to use buildpacks to create optimized Spring Boot containers — fast, secure, and cloud-ready — with just one command. We’ll show what happens under the hood: automatic dependency detection, layered image creation, memory tuning, SBOM generation, and how to tweak builds with just a few plugin options. Need faster startup, smaller image size, or JFR monitoring? Buildpacks can handle it — and we’ll show you how.

Videos
card image
Aug 20, 2025
Flyway in Spring Boot: Step-by-Step tutorial with Maven

Learn how to use Flyway in Spring Boot with Maven for smooth and reliable database migrations. In this hands-on tutorial, we cover everything from setting up PostgreSQL in Docker, configuring Flyway in your application, writing versioned and repeatable migrations, to using Flyway in CI/CD pipelines with GitHub Actions. Whether you’re new to Flyway or want to master schema version control in Spring Boot, this video will guide you step by step.

Videos
card image
Aug 14, 2025
Stop Using DTOs – A Cleaner Way for Your Java APIs

Still creating DTOs for every API in your Spring Boot project? You might be overcomplicating things. In this video, we show why DTOs aren’t always necessary and how to replace them with @JsonIgnore, @JsonView, and Jackson Mixins. You’ll see real examples of hiding sensitive fields, creating role-based views, and cutting boilerplate — all while keeping your API safe, clean, and easy to maintain.