Summary
Office2LLM is designed around local-first conversion. Ready PPTX and DOCX workflows read the selected file in browser-side code and generate previews and ZIP downloads in the current page session.
What we do not collect
- No account is required for ready PPTX or DOCX workflows.
- No server-side conversion history is created by the ready local converter.
- No cloud storage is required for the generated package.
How local processing works
- You select a PPTX or DOCX file in the browser.
- Office2LLM extracts supported structure locally, such as slide text, document sections, notes, images, tables, charts, warnings, and metadata.
- Markdown, HTML, JSON, manifest, and assets are prepared for preview.
- The ZIP package is generated before download in the same browser session.
Ready Office formats
PPTX and DOCX converters are available as browser-local workflows. DOCX headers and footers are stored as metadata by default, while low-signal footer content such as standalone page numbers may be filtered from the main LLM input.
Planned Office formats
XLSX and additional structured Office routes are planned. Until those converters are implemented and tested, they should not expose a fake upload entry or imply that conversion is available.
Future server-enhanced modes
If future workflows require server-side processing, such as LibreOffice conversion, visual parsing, or enhanced document repair, those modes should be clearly labeled before any upload and remain separate from the ready local workflow.
Clearing local data
Because ready conversion happens in the browser, closing the tab clears in-memory conversion state. Browser cache or site data can also be cleared from browser settings when needed.