What is a native executable in Quarkus?

A native executable is a standalone binary produced by compiling a Quarkus application ahead-of-time with GraalVM's native-image tool, bundling the application code, a minimal runtime, and only the JDK classes actually reachable by that specific application into one self-contained file.

Unlike a regular JAR, it doesn't need a separately installed JVM to run — the binary itself is the executable, which is part of why it starts so fast and uses less memory: there's no general-purpose JVM sitting underneath doing class loading and JIT compilation for code paths this particular application never uses.

The trade-off is that native images are platform-specific (a Linux native executable won't run on Windows), the build itself takes noticeably longer and uses more memory than a normal compile, and some dynamic Java features — reflection, dynamic class loading, JNI — need explicit configuration to work correctly, since GraalVM's static analysis can't always discover them automatically.