> For the complete documentation index, see [llms.txt](https://docs.keycloakify.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keycloakify.dev/features/compiler-options/keycloakversiontargets.md). # keycloakVersionTargets {% embed url="" %} By default, Keycloakify generates diffrent jar files, each one meant to be used with a given Keycloak version range. {% hint style="info" %} Yes, **Keycloak 26 is supported**. Use the *keycloak-theme-for-kc-all-other-version.jar*. {% endhint %}

However you might want to customize this behavior. If you know ahead of time what Keycloak you theme will using you can build only for this version using the `keycloakVersionTargets` build option. {% tabs %} {% tab title="Vite" %}

import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import { keycloakify } from "keycloakify/vite-plugin";

// https://vitejs.dev/config/
export default defineConfig({
    plugins: [react(), keycloakify({
        // ...
        keycloakVersionTargets: {
            // It depends of your configuration
            // Watch the video to learn more
        }
    })]
});

{% endtab %} {% tab title="Webpack" %}

{
    "keycloakify": {
        // ...
        "keycloakVersionTargets": {
           // It depends of your configuration, if you are implementing
           // an Multi-Page account theme or not and of the version
           // of keycloakify you are using.  
           // Since TypeScript can't help you here the best option 
           // to know what ranges are available is to clone the vite
           // starter, pin your Keycloakify specific version and 
           // set the account implementation that you have in your project.
           // Watch the video to learn more.
           // The vite starter: https://github.com/keycloakify/keycloakify-starter
    }
}

{% endtab %} {% endtabs %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.keycloakify.dev/features/compiler-options/keycloakversiontargets.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.