Skip to main content
Not every file needs a commercial OCR stack. On hosted Unfold, LiteParse and PDF Inspector run as focused engines. Use them first when the document is likely born-digital or you only need a light pass. This guide starts the expensive engine only after the cheap result looks weak. That is different from Fast preview, then full parse, which starts both engines immediately for UI latency.

Pick a cheap engine

Do not request tables from LiteParse. Hosted create/parse rejects unsupported outputs before provider I/O.

Escalate on the same document

Reuse one documentId. Run a LiteParse job. If the result looks weak, create a second job for the heavier engine. You avoid paying for LlamaParse when LiteParse is already good enough.
idempotencyKey on jobs belongs in the second argument to jobs.create, not inside the job body.

Habits that keep cost down

  • Triage with liteparse or pdf-inspector
  • Escalate with a second job on the same document, not a second blind parse() that re-uploads
  • Request only outputs each engine supports
  • Release stored artifacts when the pipeline finishes
  • Use Bake off engines offline to learn which engine wins on your corpus