
Modrinth · Minecraft mod
Minecraft SQLite JDBC
Up-to-date SQLite JDBC driver wrapped as a universal Forge/Fabric/Bukkit library for plugins like Dynmap and Grim.
Quick answer
Which Minecraft SQLite JDBC release matches 1.14.2 Forge?
Minecraft SQLite JDBC 3.53.2.0+2026-06-06 targets 1.12.2, 1.13, 1.13.1 with bukkit, Fabric, folia. Installation on the client is optional. Installation on the dedicated server is optional. No extra mods listed for this file.
Where it goes
Is Minecraft SQLite JDBC required on the client, server, or both?
Installation on the client is optional. Installation on the dedicated server is optional.
The source marks this as usable on both the client and server.
What else does Minecraft SQLite JDBC 3.53.2.0+2026-06-06 need?
3.53.2.0+2026-06-06 on 1.14.2 Forge. Every mod below is checked against that same setup.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add Minecraft SQLite JDBC without breaking your instance.
Built for Minecraft SQLite JDBC 3.53.2.0+2026-06-06 on 1.14.2 Forge. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use 3.53.2.0+2026-06-06. It targets 1.12.2, 1.13, 1.13.1 with bukkit, Fabric, folia; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
Installation on the client is optional. Installation on the dedicated server is optional.
- 04
Pick the file you checked
Use the “Get this file” button beside 3.53.2.0+2026-06-06. It opens that exact file at the source.
About this project
What does Minecraft SQLite JDBC add?
SQLite JDBC for Minecraft
A maintained fork of the dormant SQLite JDBC for Minecraft mod, now tracking the latest Xerial sqlite-jdbc release with auto-bumps whenever upstream cuts a new version.
The mod does nothing on its own — it ships the SQLite JDBC driver onto the server's classpath so other plugins/mods that want to read or write .db/.sqlite files via JDBC don't each have to bundle their own copy.
Typical consumers: Dynmap, Plan, LuckPerms, Grim Anti-Cheat, and any plugin that wants embedded SQLite without redistributing 10MB of native binaries themselves.
What's in the jar
org.xerial:sqlite-jdbc:3.53.0.0 plus minimal loader stubs for Spigot, Forge 1.12, Forge 1.13–1.16, Forge 1.17–1.20, NeoForge 1.21+, and Fabric. The driver classes stay at their canonical org.sqlite.* paths — no relocation — so consumers find them with plain Class.forName("org.sqlite.JDBC"). META-INF/services/java.sql.Driver is preserved so the driver auto-registers with DriverManager.
The xerial driver bundles native SQLite binaries for every common platform/architecture (linux x64/aarch64, macos x64/arm64, windows x64). They get extracted to the JVM's tempdir on first use.
Compatibility
| Loader | MC versions | Notes |
|---|---|---|
| Bukkit / Spigot / Paper / Folia / Purpur | 1.8 → current | drop into plugins/ |
| Fabric | 1.16.1 → current | needs Fabric Loader 0.14+ |
| Forge | 1.12 → 1.20 | universal jar, no Mixins |
| NeoForge | 1.21 → current | drop into mods/ |
Java 8+ required. Plain BukkitAPI servers without Java 8 (anything older than ~1.8.8) won't be able to load any modern xerial release; that's an upstream constraint, not this mod.
When you actually need this mod
CraftBukkit/Spigot/Paper have shipped sqlite-jdbc on the server's parent classloader since the 1.4-era ebeans commit. Plugin classloaders delegate parent-first, so for the default JDBC path (Class.forName("org.sqlite.JDBC") / DriverManager.getConnection) the bundled driver always wins, regardless of what's in plugins/. Tested empirically on Paper 1.12.2 and 1.21.11.
You need this mod when:
- You're on Fabric or NeoForge — vanilla Minecraft ships no JDBC drivers at all
- You're on a Bukkit fork that's stripped the bundled driver (rare, but happens on minified server builds)
- You want a newer SQLite engine version than your server bundles — for
RETURNING,STRICTtables, modern UPSERT on a 1.8–1.12 server, or just to track the latest Xerial release. See Using a newer engine via the public API below.
Using a newer engine via the public API
The default path uses the bundled driver. To use this mod's driver instead, your plugin softdepends on this holder and calls MinecraftSqliteJdbc.connect(url) directly:
// in your plugin.yml
softdepend: [sqlite-jdbc]
// in your plugin code
Connection c;
try {
c = MinecraftSqliteJdbc.connect("jdbc:sqlite:foo.db");
} catch (NoClassDefFoundError | ClassNotFoundException notInstalled) {
// holder isn't installed — fall back to the bundled driver
c = DriverManager.getConnection("jdbc:sqlite:foo.db");
}
MinecraftSqliteJdbc wraps a child-first URLClassLoader pointing at this jar's URL, parented to the platform classloader so org.sqlite.* must come from this jar (not the bundled chain). The returned Connection is a standard java.sql.Connection — keep your casts to java.sql.* interfaces; the impl class org.sqlite.SQLiteConnection lives in the child-first classloader and won't down-cast across the boundary.
Verified on Paper 1.12.2 (bundled engine 3.21.0) — same JVM, same boot:
baseline DriverManager.getConnection → engine 3.21.0
MinecraftSqliteJdbc.connect() → engine 3.53.0
API surface (all static):
| Method | Returns |
|---|---|
connect(String url) |
open Connection through this driver |
connect(String url, Properties props) |
as above with props |
driver() |
the java.sql.Driver instance |
engineVersion() |
SQLite engine version (e.g. "3.53.0") |
driverVersion() |
driver version string (e.g. "3.53.0.0") |
eagerInit() |
warm the classloader at plugin enable |
shutdown() |
release file handles + JNI on plugin disable |
Grim Anti-Cheat's SQLite backend uses this API automatically when this holder is installed and ships a newer engine than the bundled one — see Grim's Database wiki page.
Bundled SQLite engine versions on common Bukkit lines
For reference if you're wondering what engine version your server actually ships:
| CraftBukkit / Paper line | Bundled SQLite engine |
|---|---|
| 1.8 – 1.10 | 3.7.2 |
| 1.11 | 3.16.1 |
| 1.12 | 3.21.0.1 |
| 1.13 | 3.25.2 |
| 1.14 | 3.28.0 |
| 1.15 | 3.30.1 |
| 1.16 – 1.17 | 3.34.0 |
| 1.20.6 | 3.45.3.0 |
| Paper 1.21.4 | 3.47.0.0 |
| Paper 1.21.5 – 1.21.11 | 3.49.1.0 |
| master / 26.x | 3.51.3.0 |
This mod ships engine 3.53.0.0 (or whatever the latest xerial release is), but none of that matters on Bukkit-family servers — the bundled engine is what actually runs your queries. If you need a newer engine for features like RETURNING (3.35+) or STRICT tables (3.37+), upgrade to a Paper version that bundles a recent enough driver, or move that workload to Fabric/NeoForge where you can control the driver.
Using it from a plugin or mod
Declare sqlite-jdbc as compileOnly:
compileOnly("org.xerial:sqlite-jdbc:3.53.0.0")
Probe at startup:
try {
Class.forName("org.sqlite.JDBC");
} catch (ClassNotFoundException e) {
getLogger().warning("SQLite backend disabled — install minecraft-sqlite-jdbc");
return;
}
try (Connection c = DriverManager.getConnection("jdbc:sqlite:" + dataDir.resolve("data.db"))) {
// ...
}
On Paper 1.17+ each plugin's classloader is isolated. Add this mod to your plugin.yml softdepend so the driver classes are visible to your plugin:
softdepend: [minecraft-sqlite-jdbc]
Fabric and NeoForge unify all mods on one classloader, so no equivalent declaration is needed there.
Versioning
The jar version tracks Xerial's sqlite-jdbc release one-to-one. 3.53.0.0+2026-04-14 ships engine 3.53.0.0; the suffix is the build date. A scheduled GitHub Action checks Maven Central daily — when xerial cuts a new release, an auto-merge PR opens here and the Modrinth release goes out automatically.
License
Apache 2.0 (Xerial / Taro L. Saito). The repackage adds no functional changes and inherits that license. Full text in LICENSE.
Issues, source: GitHub.
Project description from Modrinth.
Pick your setup
Minecraft SQLite JDBC by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
26.1.1
4 loader builds26.1
4 loader builds1.21.11
4 loader builds1.21.10
4 loader builds1.21.9
4 loader builds1.21.8
4 loader builds1.21.7
4 loader builds1.21.6
4 loader builds1.21.5
4 loader builds1.21.4
4 loader builds1.21.3
4 loader buildsShowing the newest 12 of 50 game versions. Older files are in the list below.
Check the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
Minecraft SQLite JDBC versions and loaders
3.53.2.0+2026-06-06
sqlite-jdbc-3.53.2.0+2026-06-06-all.jar
6 Jun 2026
3.53.2.0+2026-06-06
sqlite-jdbc-3.53.2.0+2026-06-06-all.jar
6 Jun 2026
3.53.1.0+2026-05-07
sqlite-jdbc-3.53.1.0+2026-05-07-all.jar
7 May 2026
3.53.0.0+2026-04-14
sqlite-jdbc-3.53.0.0+2026-04-14-all.jar
26 Apr 2026
3.53.0.0+2026-04-14
sqlite-jdbc-3.53.0.0+2026-04-14-all.jar
26 Apr 2026
3.53.0.0+2026-04-14
sqlite-jdbc-3.53.0.0+2026-04-14-all.jar
26 Apr 2026
3.53.0.0+2026-04-14
sqlite-jdbc-3.53.0.0+2026-04-14-all.jar
25 Apr 2026
3.53.0.0+2026-04-14
sqlite-jdbc-3.53.0.0+2026-04-14-all.jar
14 Apr 2026
3.51.3.0+2026-03-17
sqlite-jdbc-3.51.3.0+2026-03-17-all.jar
17 Mar 2026
3.51.2.0+2026-02-10
sqlite-jdbc-3.51.2.0+2026-02-10-all.jar
10 Feb 2026
3.51.1.0+2025-12-01
sqlite-jdbc-3.51.1.0+2025-12-01-all.jar
2 Jan 2026
3.51.0.0+2025-11-13
sqlite-jdbc-3.51.0.0+2025-11-13-all.jar
13 Nov 2025
Looking for an older file? The official Modrinth project page is in Resources.