LLMind web converter
For non-developers, or for one-off enrichments, app.llmind.org is the lowest-friction way to use LLMind. Drag a file in, get an enriched version back. Same signed semantic layer, same XMP namespace, same portability as the CLI. No install, no CLI knowledge.
What it does
Same engine as the CLI, wrapped in a browser interface. Upload a PDF, image, or audio file. The converter enriches it in the browser (or with a server-side pass for heavier workloads). The enriched file is downloaded; the original plus the new XMP packet are yours. Every enriched file carries the same signed semantic layer that the CLI produces, written into the same https://llmind.org/ns/1.0/ XMP namespace.
Supported file types
JPEG, PNG, PDF, MP3, WAV, M4A. More formats on the roadmap — check back soon. Files can be any reasonable size for browser upload (determined by the backend's timeout). For batch enrichment or integration into a pipeline, the CLI is faster.
Privacy stance
The current implementation sends files to a FastAPI backend for enrichment, then returns the result to the user. Files are not persisted beyond the request. For stricter privacy requirements — regulated content, sensitive files — use the CLI locally. That's the recommended path for regulated industries. A full client-side converter (in-browser WASM) is on the Sprint 3+ roadmap.
Try it
or try the CLI for batch enrichment
Related resources
- Use cases — See where the web converter fits into your workflow
- Comparisons — How LLMind differs from alternatives
- Learning resources — Understand file enrichment concepts
- MCP integrations — Connect enriched files to your agents
- Specification — The formal standard
- Documentation — API and CLI reference