API v1
Compatibility, limits, and validation boundaries
Use these limits to pre-filter source files and design quality gates before a migration or downstream AI workflow.
| Limit | Value |
|---|---|
| Maximum source file | 4 MiB (4,194,304 bytes) |
| Accepted extensions | .doc, .ppt, .xls |
| Required source container | Valid Office 97-2003 OLE/CFB file matching the extension |
| Task identifier | 32 lowercase hexadecimal characters |
| Result retention | Approximately 30 minutes |
| Download URL lifetime | 5 minutes; query again for a fresh URL during retention |
| Task metadata expiry | Scheduled after 24 hours; DynamoDB TTL deletion is asynchronous |
Rejected inputs
- Encrypted, corrupted, empty, disguised, or non-OLE/CFB files.
- Unsupported legacy variants.
- XLS external-workbook references.
- Documented XLS database-formula edge cases.
Macros and active content
Macros are never executed. XLS VBA preservation is disabled. Do not use this API when the destination workflow depends on executable macros or an exact macro-enabled artifact.
Migration validation
- Start with representative complex samples from each business unit.
- Compare structural counts such as pages, slides, sheets, tables, and images where available.
- Render and visually sample DOCX and PPTX outputs.
- Inspect formulas, dates, number formats, borders, fills, and merged cells in XLSX.
- Verify the behavior of the actual downstream parser or destination system.
Fidelity: conversion targets structural compatibility, not universal pixel-perfect equivalence. Validate representative business documents before a large migration or production AI ingestion.