Convert HTTP requests to Markdown.
Drop a saved .http or .rest file and read every request as clean Markdown. 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.
Raw calls,
read at a glance.
A .http or .rest file is a wall of methods, URLs and headers meant for a request runner, not a reader. Converting lays each call out as readable, shareable Markdown.
### Get users
GET https://api.example.com/users
Authorization: Bearer TOKEN
Accept: application/json
## `GET` https://api.example.com/users
Headers:
- Authorization: Bearer TOKEN
- Accept: application/json
Everything you
actually need.
Saved request files in, clean Markdown out, with no server and no account anywhere.
It never leaves your browser
The .http file 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.
```
{ "name": "ada" }
```
Body in a fence
Each request body is wrapped in a code fence, so JSON and form payloads stay readable.
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.
The real requests come through faithfully; only comments and filler lines are skipped. These are the same notes the Formats list shows for HTTP request files, so the page never drifts from what the converter does.
Kept
4- Method and URL
- Headers
- Body (in a code fence)
- Multiple requests
Ignored
3- Comments
- Blank lines
- Non-request lines
### Get users
GET https://api.example.com/users
Authorization: Bearer TOKEN
Accept: application/json
```
{ "active": true }
```
HTTP request questions,
answered.
Everything worth knowing before you drop in a .http file.
Other converters.
Working with more than request files? These convert the same way: privately, in your browser.
AbiWord to Markdown
.abw
AbiWord word-processor documents.
Hangul to Markdown
.hwpx
Korean Hangul Office documents.
InDesign / IDML to Markdown
.idml · .icml
Adobe InDesign layout exchange files.
Excel to Markdown
.xlsx
Microsoft Excel workbooks.
OpenDocument Sheet to Markdown
.ods · .fods
LibreOffice Calc spreadsheets.
CSV to Markdown
.csv
Comma-separated value tables.
TSV to Markdown
.tsv
Tab-separated value tables.
Parquet to Markdown
.parquet
Columnar big-data tables.