Jetformat

Supported and unsupported files

Use the extension and the requested operation to decide whether Jetformat is the right tool before running a job.

By Jetformat

Supported

  • word, excel, ppt to-pdf for DOCX, XLSX, PPTX.
  • Inspect and edit existing Office files (templates, cells, comments, slides).
  • html to-pdf from a file, directory, or URL (beta).
  • pdf to-word, plus info, merge, extract, fill, encrypt, annotate, attach, and render.
  • text from Office files and PDFs with a text layer.
  • validate for Office, PDF, fonts, EMF, and XMP.

Out of scope

  • Legacy .doc, .xls, and .ppt files.
  • Macro-enabled .docm, .xlsm, and .pptm files.
  • OCR for scanned pages.
  • Password-protected PDFs, until pdf decrypt.

Before you run a job

Do not rename an extension to make an unsupported file look supported. Save it from the source application as DOCX, XLSX, or PPTX, then run Jetformat against the new path.

Read what Jetformat does.

Identify why the input cannot be used

An unsupported input is a file format or source feature outside the selected command’s capabilities. This is different from a corrupt file, a missing local path, or an output filename that already exists. Preserve the actual error instead of treating every failed conversion as an unsupported format.

Situation Appropriate check What not to assume
Legacy Office extension Obtain a supported export from the source application Renaming the suffix converts the format
Scanned PDF Inspect whether usable text exists PDF-to-Word performs OCR
Protected PDF Confirm authorized access and decrypt where appropriate The visible filename proves it can be read
Unsupported chart or diagram Review the command’s feature limits A successful exit preserves every object
Existing output file Choose a new path or deliberate overwrite policy The input format caused the failure

Recover a supported workflow

  1. Confirm the source path exists and the selected command matches its real format.
  2. Run validation and keep the error if the file cannot be parsed.
  3. If needed, export a supported copy from an application that understands the original.
  4. Run the Jetformat operation on the new copy and inspect the result.
  5. Report any remaining unsupported content before distributing the derivative.

Do not discard the original during diagnosis. A structurally valid input can still depend on a missing font or an unimplemented feature. Use font and layout troubleshooting for appearance differences after a successful conversion, and text extraction versus OCR when the desired words exist only in scanned images.

Last updated