Convert OpenAPI / Swagger to Markdown.
Drop an OpenAPI or Swagger spec, in JSON or YAML, and get a clean Markdown summary of the API in seconds. It runs entirely in your browser, so your file never leaves your device.
Drag & drop your files
or
Optimize for AI & RAG
Extra cleanup for LLM ingestion: strip HTML, fix smart quotes, tidy Unicode and spacing.
Add YAML front matter
Prepend a metadata block (title, source, date, word & token counts) for knowledge bases and RAG.
Add table of contents
Build a linked index from the headings. Handy for long documents.
Export RAG chunks (.json)
Split the result into retrieval-ready chunks. Download per file from the result panel.
Most converters quietly upload your documents to a server. This one physically can't.
A spec is for
machines.
An OpenAPI file is dense nested JSON or YAML, easy for tools to parse but hard to read. Converting flattens it into a readable Markdown outline of every endpoint.
openapi: 3.0.0
info:
title: Petstore
paths:
/pets:
get:
summary: List pets
# Petstore
## GET /pets
List pets
Everything you
actually need.
An OpenAPI or Swagger spec in, a clean Markdown summary out, with no server and no account anywhere.
It never leaves your browser
The spec is read and converted on your own device. Nothing is uploaded to any server, ever.
# Heading
- point one
3 chunks
AI & RAG ready
Optional cleanup, YAML front matter, a table of contents and RAG chunk export.
Works offline
Once the page has loaded you can switch off your connection and it keeps converting.
Endpoint summary
Each path and method becomes a heading, with its summary, description and parameter names below.
Unicode safe
Accents, symbols and non-Latin scripts come through intact as UTF-8.
Free, and unlimited
No sign-up, no quotas, no watermarks. Convert one file or a thousand; it all runs the same way, on your own device.
What survives
the trip.
Honest about what comes through, and what doesn't. These are the same notes the Formats list shows for OpenAPI / Swagger, so the page never drifts from what the converter really does.
Kept
4- Title & version
- Description
- Paths & methods
- Parameter names
Dropped
4- Request bodies
- Responses
- Schemas
- Security & examples
GET /pets
summary: List pets
parameters: limit, offset
responses:
200: array of Pet
schema: $ref Pet
example:
id: 7
name: Rex
OpenAPI questions,
answered.
Everything worth knowing before you drop in a spec.
Other converters.
Working with more than API specs? These convert the same way: privately, in your browser.
GML to Markdown
.gml
Geography Markup Language.
Garmin TCX to Markdown
.tcx
Garmin training activities.
NMEA to Markdown
.nmea
GPS receiver sentences.
IGC to Markdown
.igc
Glider flight logs.
draw.io to Markdown
.drawio
diagrams.net drawings.
Excalidraw to Markdown
.excalidraw
Hand-drawn-style sketches.
BPMN to Markdown
.bpmn
Business process diagrams.
Vega / Vega-Lite to Markdown
.vega · .vl
Data visualization specs.