Affinity for iPad 2026: What If an InDesign File's Layout Changes After Import?

On November 2, 2026, Affinity announced that Affinity for iPad can import InDesign files, while noting that some advanced formatting may need manual adjustment (official launch notes). So if an imported page looks different, work from a copy, identify exactly what changed, and return to the original app when complex formatting affects delivery. Preserved page structure, text frames, or basic styles do not guarantee a perfect match.

This guide is for designers moving an InDesign project into Affinity for iPad, freelance layout artists checking whether a client file is still safe to edit, and small teams handing documents between apps or devices.

Last updated November 9, 2026. The import and formatting statements were checked against Affinity's iPad product page and official launch notes. Confirm those pages again before a production handoff if the app has been updated since this review.

Start with the type of change, not the assumption that the file is broken

An imported page can differ from its source in several ways. The first task is to separate a content problem from a formatting change and from a difference that appears only on screen.

Make a duplicate before changing anything. Keep the original InDesign document untouched, and record which pages or objects look different. If you can, compare the imported file with a reference PDF exported from the original document. That gives you a visual target without relying on memory.

Classify each discrepancy:

• Missing content: words, images, or other elements present in the source are absent from the import.
• Changed appearance: the content is present, but font appearance, spacing, line breaks, or styling differs.
• Moved or resized object: an image, frame, table, or other element no longer sits where expected.
• Screen-only difference: the page looks different while open, but the exported output may not share the same discrepancy.

This classification prevents a common mistake: adjusting every page before confirming whether the problem is a font substitution, a text-flow change, or a display difference. It also gives a team a useful record to share when someone else needs to review the document.

Protect the source file: don’t overwrite the original InDesign document with an imported or edited copy. Preserve it until the final layout and the exported deliverable have both been checked.

Compare page structure before adjusting individual elements

Affinity's published description of import support is not a promise that every feature in every source document will map identically. Check the document as a whole before fixing isolated details.

Begin with page order and page count. Then compare the layout from the outside in:

• Do all expected pages appear, in the correct order?
• Are the text frames present, and do they connect in the intended reading sequence?
• Do images remain on the right pages and in the right frames?
• Are margins and large layout blocks still consistent with the source?
• Does the same discrepancy appear on multiple pages, or only in one location?

If a whole section appears to have shifted, first check page order and frame relationships. If only one image has moved, record that object and page rather than assuming the entire file imported incorrectly.

A design team handing off work between devices should also decide which copy is authoritative. Keep a clear source file and a separate working copy, and avoid parallel edits to both. For a wider handoff process, check the xcodeops FAQ for service and workflow information, then document where the active project file lives and who is responsible for the next review.

Diagnose text and font changes separately

When a page changes mainly around text, check the font before changing frame sizes. A substituted or unavailable font can alter character widths and line breaks, which can then push text into other areas of the page. A paragraph style may also appear different even when the words themselves remain intact.

Compare the source and imported version in this order:

• Check the font family and style applied to the affected text.
• Compare paragraph settings, such as alignment, spacing, and indentation.
• Look for new line breaks, clipped text, or overflow from a frame.
• Check whether a difference affects one paragraph or a chain of linked frames.
• Confirm that the text content itself is complete before adjusting layout.

Adobe's guide to packaging font files for a project explains why font availability matters when documents move between environments. It does not establish that a particular font will be available or render identically in Affinity for iPad. Check the actual font used by the project and the app's current support before relying on a visual match.

If the change is limited to a small, independent text area, you may be able to correct it in the imported copy. If text has reflowed across several connected frames or changed the approved page composition, return to the source application for the correction. That keeps a local fix from creating a second, harder-to-review layout problem.

Inspect tables and anchored objects as relationships

Tables and anchored objects deserve a closer review because their position can depend on surrounding text, frame dimensions, or the way the source document handles layout. A table may still be present but no longer fit its frame. An anchored object may remain visible but no longer sit beside the paragraph it belongs to.

Choose a representative page that contains the most demanding formatting in the project. Compare the imported page with the source or reference PDF, and check:

• whether table rows and columns are all visible;
• whether text in cells is clipped or wrapped differently;
• whether an anchored object remains associated with the intended text;
• whether text flow still places nearby content in the correct order; and
• whether a correction on one page changes the layout on another.

If the project uses several kinds of complex formatting, inspect each kind rather than assuming one successful page proves the whole document is safe. Record the page and the affected element. That makes it easier to decide whether the change can be fixed locally or whether the source app is the safer place to make the correction.

An INDD document and an IDML exchange file are not interchangeable names for one identical working copy. Adobe's documentation covers saving and exporting InDesign documents; use the format that matches the handoff agreed by the team, and retain the source file. Import support does not by itself confirm that every feature in a particular INDD or IDML file will survive unchanged.

Decide whether to continue editing or return to the source app

The decision depends on the job's acceptance criteria, not on whether the file opens. If page structure, text flow, fonts, and object placement meet the task requirements, continue in the duplicate and verify the output. If a discrepancy affects a client-approved design, print specification, or complex text relationship, fix it in the original application where the source layout can be checked directly.

Before treating an imported file as print-ready, check the PDF you plan to deliver. Adobe's guide to creating print-ready PDF files and its preflight profile documentation explain production checks in InDesign. Adobe also documents how to package files for output. These references describe the source-app workflow; they do not certify an imported Affinity file. Follow the printer's requirements and inspect the actual file being delivered.

Use this decision checklist before committing to the next step:

• [ ] I kept the original source file and made a separate working copy.
• [ ] I compared page order, page count, text frames, and image placement with a reference.
• [ ] I checked whether text changes come from font availability, style differences, or reflow.
• [ ] I inspected tables and anchored objects where the project uses them.
• [ ] I verified the exported PDF against the approved layout and delivery requirements.
• [ ] I know which application and file copy the team will treat as the final source.

If any of the checks involving text flow, tables, anchored objects, or print output fails, return to the source app before making the imported copy your production master. For projects that pass, keep the source copy and record which edits were made in Affinity for iPad.

FAQ: InDesign imports and delivery checks

Can Affinity for iPad open an InDesign file?

Affinity's official launch information says the iPad app supports importing InDesign files. That confirms an import route, not a guarantee that every document will look or behave exactly as it did in its original app. Open a duplicate first, then compare page count, text flow, fonts, and object placement before editing the working file.

Why did my text styles change after importing from InDesign?

A visual difference can come from a substituted font, a changed paragraph style, or reflowed text; these are different problems and need different fixes. Compare the font and paragraph settings with the source document, then inspect line breaks and text-frame overflow. If the change affects multiple linked frames, return to the source app before making broad edits.

How should I check tables and anchored objects in an imported IDML file?

Choose a representative page and check whether each table still fits its frame, whether text remains in the intended order, and whether anchored objects stay beside the correct paragraph. Compare with a reference export from the source document. If the relationship between an object and its text has changed, treat it as a layout issue rather than assuming the file is damaged.

Can I send an InDesign file imported into Affinity for iPad to a print shop?

Only after you verify the final output against the printer's specifications. Check page size, fonts, image placement, text flow, and the exported PDF, then run a preflight in the application used for final production when possible. If a table, font substitution, or anchored object could affect the approved design, do not use the imported document as the final print master.

Match the workflow to the delivery risk

If the iPad app or the current desktop setup can complete the job and pass the checks, there is no reason to add a remote machine. When a correction genuinely requires a Mac version of the application, however, the alternatives have real costs: buying a Mac may be disproportionate for an occasional repair; using another desktop environment may not provide the required Mac app; and remote access introduces connectivity, file-transfer, and review steps.

For that limited correction stage, renting a Mac from xcodeops can let a designer use a Mac environment without buying hardware for a one-off task. It is not a substitute for checking the document or the final print output, and it is a poor fit if the work requires a local physical connection or sustained use that makes ownership more suitable. Teams handling client files should also review the xcodeops data privacy information before deciding how to transfer project documents. If the source app is already available and the imported file passes the acceptance checks, stay with the workflow that already works.

Frequently asked questions