Skip to main content
KiwiFS can export your entire knowledge base (or a subset of it) as JSONL, CSV, or Parquet. You can export from the CLI or the REST API.

Formats

Each line is a JSON object representing one file. Fields come from frontmatter.
With --include-content, each object includes the full markdown body.
With --include-links, each object includes link data.
With --include-embeddings, each object includes a vector embedding array. A .schema.json sidecar file is also written alongside the output file, describing the embedding model and dimensions.

CLI usage

Use the kiwifs export command to export from the command line.

CLI flags

REST API

Export your knowledge base over HTTP using the /api/kiwi/export endpoint.

Query parameters

The response streams as application/x-ndjson (JSONL) or text/csv (CSV) with chunked transfer encoding. You can pipe the response directly into downstream tools.

Embeddings sidecar

When you export with --include-embeddings, KiwiFS writes a .schema.json sidecar file next to the output file. This file describes the embedding model used and the vector dimensions.
vectors.schema.json
Embeddings are only available if you have configured a vector search provider (such as pgvector with an OpenAI API key).

Common recipes

Export frontmatter as JSONL and commit it alongside your knowledge base for a searchable metadata snapshot.
Export with content and embeddings, then feed the output into your static site search pipeline.
Export as CSV and load into your warehouse using standard ETL tools.
Pipe JSONL output to jq for ad-hoc filtering and transformation.
For large knowledge bases, use --path to scope the export to a subdirectory and --limit to cap the number of files. This keeps export times predictable.

Document export (PDF, HTML, slides)

To render markdown into PDF, HTML, slide decks, or static sites, use Document export (POST /api/kiwi/export/document or MCP kiwi_export_document).
Last modified on May 31, 2026