# Markdown Studio

> Write Markdown, preview it in the browser, and convert it to PDF, HTML, TeX, or DOCX.

The editor is at `/`. All paths in these documents are relative to the origin serving this documentation; keep its scheme, hostname, and port.

For an agent creating a file, send Markdown in a JSON body to `POST /export` and save the response bytes. For a user who needs a shareable output, construct a compressed `GET /export` URL. A shared editor link uses the same query parameters at `/`.

The browser preview runs locally using the bundled JavaScript Markdown parser. Exports send the document to the server and use Pandoc. No API key is required on a public deployment. If the deployment shows a sign-in page, use an authorized authenticated session; these files do not bypass that gate.

## Documentation

- [HTTP API and link generation](/docs/tool-use.md): Request bodies, compression, options, response formats, limits, fonts, filenames, and errors.
- [Markdown syntax guide](/docs/markdown.md): The same supported syntax examples shown in the editor's guide.
- [Documentation index](/llms.txt): A concise entry point for agents.
- [Complete documentation](/llms-full.txt): Overview, HTTP usage, and syntax examples in a single response.

## Using the editor

Edit the Markdown source to update the preview after a short debounce. Choose Serif or Sans, choose whether to embed fonts, and select the output format. The button saves the file as a download. Tick "Open in new tab" to switch it to Export, which opens the resulting file in a new tab instead. Copy link shares the editable document.

When a document is too large for a shared URL, Copy link is disabled and "Open in new tab" is unchecked and disabled, leaving download as the only option. Shortening the document restores the previous choice. Live preview and downloading remain available. Very large individual code blocks remain readable without token highlighting.

Photo can resize and convert an image in the browser and produce an embedded Markdown image. The HTTP converter accepts Markdown; there is no photo-upload or OCR API.

Shared URLs contain compressed, reversible document content. Anyone receiving a link can read its content. POST downloads avoid putting that content in the URL. Only send a document to the export server when that is appropriate for the user's request.