Gradle to Maven Converter
Free online Gradle to Maven converter. Turn build.gradle or build.gradle.kts dependencies and plugins into Maven pom.xml snippets instantly.
Loading tool...
What is Gradle to Maven Converter?
The Gradle to Maven Converter is a free online tool that translates Gradle build scripts into Maven pom.xml syntax. Paste a build.gradle or build.gradle.kts file and instantly get equivalent Maven dependencies and plugins, with configuration-to-scope mapping, preserved exclusions, and TODO markers for version catalog aliases. Everything runs locally in your browser.
Key Benefits
- Saves hours of manual migration work when moving a project from Gradle to Maven.
- Reduces transcription errors in group IDs, artifact IDs, and version strings.
- No installation or account required — works in any modern browser.
- Private and offline-capable: build scripts never leave your machine.
Common Use Cases
- •Migrating a legacy Gradle project to a Maven-based enterprise build pipeline.
- •Generating pom.xml snippets for tools that only understand Maven (some IDE plugins, CI templates).
- •Comparing dependency sets between Gradle and Maven during a dual-build evaluation.
- •Onboarding Java developers who know Maven but are reading a Gradle codebase for the first time.
How to Convert Gradle to Maven
- Paste your Gradle script: Copy the contents of your build.gradle or build.gradle.kts file and paste them into the input area, or click Groovy sample / Kotlin DSL sample to try the tool instantly.
- Review the parsed summary: Check the badges showing the detected DSL, dependency count, and plugin count to confirm the script was read correctly.
- Choose the output mode: Keep Generate full pom.xml checked for a complete file with project coordinates, or uncheck it to get only the dependencies snippet for pasting into an existing pom.
- Copy or download the result: Click Copy pom.xml to send the XML to your clipboard, or Download to save it as pom.xml. Resolve any TODO comments for version catalog aliases before building.
Key Features
- Parses both Groovy DSL (build.gradle) and Kotlin DSL (build.gradle.kts) syntax with automatic detection.
- Maps 16 Gradle configurations to Maven scopes, including implementation, compileOnly, annotationProcessor, kapt, ksp, and test variants.
- Preserves transitive dependency exclusions as Maven exclusion elements.
- Converts well-known Gradle plugins (Spring Boot, Kotlin, node-gradle) to their Maven plugin coordinates and versions.
- Flags version catalog aliases and omitted versions as TODO comments so nothing breaks silently.
- Generates a complete pom.xml or a dependencies-only snippet, with copy and download options. 100% client-side.
Frequently Asked Questions
Which Gradle syntax does the converter support?
Both the Groovy DSL (build.gradle files with single-quoted dependency strings) and the Kotlin DSL (build.gradle.kts files with parenthesized function-call notation). The DSL is detected automatically from your input.
How do Gradle configurations map to Maven scopes?
implementation, api, and compile map to the default compile scope (no scope tag emitted). compileOnly, annotationProcessor, kapt, and ksp map to provided. testImplementation, testCompile, and testRuntimeOnly map to test. runtimeOnly maps to runtime.
What happens with version catalog aliases like libs.guava?
The converter cannot resolve aliases without your gradle/libs.versions.toml file, so it emits the dependency with a TODO comment containing the alias. Fill in the real group, artifact, and version from your catalog, or paste resolved coordinates instead.
Are dependency exclusions preserved?
Yes. Both Groovy exclude group: ..., module: ... syntax and Kotlin exclude(group = ..., module = ...) syntax are translated into Maven exclusion elements inside the generated dependency.
Does the tool upload my build script anywhere?
No. Parsing and generation happen entirely in your browser with JavaScript. Nothing is sent to a server, and the tool works offline, so proprietary build scripts stay on your device.