Two PDFs that look identical can behave very differently in an editor. The origin matters.
Here is the difference between native and converted PDFs.
Native PDF
Authored directly as PDF — design tools like InDesign, or 'Save as PDF' from Word. Clean text layer. Embedded fonts. Predictable structure. Easiest to edit and convert.
Converted PDF
Came from elsewhere — scanned, OCR'd, exported from a database, generated by a quirky reporting tool. Text layer may be patchy. Fonts may be missing. Structure may surprise you.
Why it matters in editing
On native PDFs, edit-pdf handles text changes cleanly. On converted PDFs, especially OCR'd scans, edits sometimes need re-flowing. The editor is the same; the source affects results.
Why it matters in conversion
Convert-pdf-to-word on a native PDF often produces near-perfect output. On a converted PDF the output can be ragged. If conversion is critical, find the original source if you can.
FAQ
How do I tell if a PDF is native?
Try to select text. Clean selection and consistent fonts usually signal native.
Can I improve a converted PDF?
Re-OCR it with a good OCR tool, or ask the sender for the original source file.
Does Flint detect native vs converted?
Flint just edits both. Some operations may need light cleanup on converted PDFs.
Native is easier; converted is reality. Flint handles both — and tells you when re-OCR would help.