Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Dokka review

Free#6 of 38 in Documentation GeneratorsApi Docs

A flexible open-source choice for Kotlin and Java API documentation.

8.7/10Editor score
Visit JetBrains
Dokka8.7 Visit JetBrains

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Dokka is an open-source API documentation engine from JetBrains for developers and library teams working with Kotlin, Java, Android, and multiplatform projects. It reads Kotlin KDoc and Java Javadoc comments, making it suitable for mixed-language codebases that need a shared reference layer. The tool can also process Markdown module and package documentation, so teams can place API reference material alongside supporting project information.

Output flexibility is one of Dokka’s clearest strengths. It generates HTML, Javadoc HTML, GitHub Flavored Markdown, and Jekyll-compatible Markdown, allowing documentation to fit different publishing workflows. Documentation from multiple subprojects can be aggregated, which is useful for projects organized as several modules. Gradle, Maven, and command-line execution provide several ways to place generation into an existing build process, while plugins extend the tool for versioning, Android documentation, diagrams, and other needs. The versioning plugin adds a version selector for projects that publish documentation across releases.

Dokka is a strong fit when the priority is structured Kotlin and Java API reference output with multiple publishing options and project-level aggregation. Its open-source model also suits teams that want to incorporate documentation generation into Gradle, Maven, or CLI workflows. The main trade-off is focus: Dokka is built around API documentation from Kotlin, Java, and supported Markdown inputs, rather than positioning itself as a general-purpose documentation suite. Teams should choose it when language-aware API reference, mixed-language support, and versioned output matter most; projects seeking a broader documentation system may need a different tool or additional components.

Dokka pros and cons

  • Where it wins
    • Supports Kotlin KDoc and Java Javadoc in mixed-language projects
    • Outputs HTML, Javadoc HTML, GFM, and Jekyll-compatible Markdown
    • Runs with Gradle, Maven, CLI, and supports versioned documentation
  • Where it doesn't
    • Focused on API documentation rather than a broader documentation suite
    • Requires source comments such as KDoc or Javadoc for API content
    • Its workflow centers on Kotlin, Java, and listed Markdown inputs

Dokka fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update