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.

Tags

Tutorial
Videos
card image
Jan 20, 2026
JDBC vs ORM vs jOOQ: Choose the Right Java Database Tool

Still unsure what is the difference between JPA, Hibernate, JDBC, or jOOQ and when to use which? This video clarifies the entire Java database access stack with real, production-oriented examples. We start at the foundation, which is JDBC, a low-level API every other tool eventually relies on for database communication. Then, we go through the ORM concept, JPA as a specification of ORM, Hibernate as the implementation and extension of JPA, and Blaze Persistence as a powerful upgrade to JPA Criteria API. From there, we take a different path with jOOQ: a database-first, SQL-centric approach that provides type-safe queries and catches many SQL errors at compile time instead of runtime. You’ll see when raw JDBC makes sense for small, focused services, when Hibernate fits CRUD-heavy domains, and when jOOQ excels at complex reporting and analytics. We discuss real performance pitfalls such as N+1 queries and lazy loading, and show practical combination strategies like “JPA for CRUD, jOOQ for reports.” The goal is to equip you with clarity so that you can make informed architectural decisions based on domain complexity, query patterns, and long-term maintainability.

Watch Now
Videos
card image
Jan 13, 2026
Hibernate: Ditch or Double Down? When ORM Isn't Enough

Every Java team debates Hibernate at some point: productivity champion or performance liability? Both are right. This video shows you when to rely on Hibernate's ORM magic and when to drop down to SQL. We walk through production scenarios: domain models with many-to-many relations where Hibernate excels, analytical reports with window functions where JDBC dominates, and hybrid architectures that use both in the same Spring Boot codebase. You'll see real code examples: the N+1 query trap that kills performance, complex window functions and anti-joins that Hibernate can't handle, equals/hashCode pitfalls with lazy loading, and practical two-level caching strategies. We also explore how Hibernate works under the hood—translating HQL to database-specific SQL dialects, managing sessions and transactions through JDBC, implementing JPA specifications. The strategic insight: modern applications need both ORM convenience for transactional business logic and SQL precision for data-intensive analytics. Use Hibernate for CRUD and relationship management. Use SQL where ORM abstractions leak or performance demands direct control.

Watch Now

Further watching

Videos
card image
Feb 6, 2026
Backend Developer Roadmap 2026: What You Need to Know

Backend complexity keeps growing, and frameworks can't keep up. In 2026, knowing React or Django isn't enough. You need fundamentals that hold up when systems break, traffic spikes, or your architecture gets rewritten for the third time.I've been building production systems for 15 years. This roadmap covers three areas that separate people who know frameworks from people who can actually architect backend systems: data, architecture, and infrastructure. This is about how to think, not what tools to install.

Watch Now
Videos
card image
Jan 29, 2026
JDBC Connection Pools in Microservices. Why They Break Down (and What to Do Instead)

In this livestream, Catherine is joined by Rogerio Robetti, the founder of Open J Proxy, to discuss why traditional JDBC connection pools break down when teams migrate to microservices, and what is a more efficient and reliable approach to organizing database access with microservice architecture.

Watch Now
Videos
card image
Jan 27, 2026
Sizing JDBC Connection Pools for Real Production Load

Many production outages start with connection pool exhaustion. Your app waits seconds for connections while queries take milliseconds; yet, most teams run default settings that collapse under load. This video shows how to configure connection pools that survive real production traffic: sizing based on database limits and thread counts, setting timeouts that prevent cascading failures, and implementing an open source database proxy Open J Proxy for centralized connection management with virtual connection handles, client-side load balancing, and slow query segregation. For senior Java developers, DevOps engineers, and architects who need database performance that holds under pressure.

Watch Now