Start with the message shown by InkSmith, then use the checks below. If an import succeeded with differences, open its report before changing the document.
A PDF or IDML import looks incomplete
Open File → Last import report. Review missing links, flattened items, discarded PDF structures, and page-specific warnings. Compare the imported document with the source, especially fonts, text wrapping, images, and page edges.
For IDML, keep linked assets beside the package. For PDF, try a source export that embeds fonts and images. Importing a final PDF cannot always restore the original editable structure.
A portable template will not save
A current .inks file needs the exact required font faces and assets. Read the structured missing-font diagnostic, replace or resolve the face, and save again. InkSmith does not silently substitute a font in a newly saved portable package.
Export is limited or has a footer
Check the current edition and cached licence. Free mode has a two-page PDF cap, draft RGB output, and a small footer credit. Paid or trial grants expand those limits. See editions.
Press Control cannot connect
Check the saved server profile, readiness result, TLS and certificate details, API compatibility, and your permissions. A local template still works without Press. See Press Control.
The CLI says the output exists
Choose a new .pdf output name. The CLI intentionally does not overwrite an existing file. For other failures, inspect its JSON error.code on stderr and the exit status. See the CLI guide.
Need more help?
Use the InkSmith website for downloads and product information. When reporting an import issue, include the source format, app version, page number, and a copy of the import report. Remove private customer information from files before sharing them.