
Affinity Photo 2's Resource Manager Collect operation does not include fonts. It can gather linked document resources, but a successful collection is not proof that another computer can edit the document with identical typography. Keep image collection and font availability as separate handoff checks.
Key Takeaways
- Collect addresses linked resources; the official Photo 2 documentation explicitly excludes fonts.
- A viewing proof and an editable source serve different purposes.
- Font distribution still depends on the actual license.
Check what Collect actually gathered
The Resource Manager reference describes gathering distributed linked resources into one folder. It also recommends Save As when preparing a separate shared document and states that fonts are not part of collection. This guide concerns Photo 2; do not assume that a newer application's differently named packaging command has the same scope.
Review every linked resource status before collecting. A resource can still be displayed even when its external file is missing. Resolve missing or modified artwork as a separate problem, then collect the resources required for the handoff. Preserve your original project while preparing the shared copy.
Make a font dependency note
List the typefaces used in editable text and explain how the recipient is expected to obtain them. Record the exact family and style instead of a visual description such as “the thin headline font.” Do not add font files to a delivery merely because they are installed locally. Confirm that the relevant license permits distribution, or tell the recipient that they need their own authorized copy.
If the recipient only needs to approve appearance, include a fixed viewing export. Explain that this proof does not provide an editable font environment. If text must remain editable, agree on an available typeface or the recipient's font access before treating the project as complete.
Proposed invitation handoff
Imagine an invitation with a linked portrait, a decorative background and a licensed display face. Collect the image resources into the shared project folder, then prepare a short dependency note naming the font and the approved viewing file.
Ask the recipient to open the shared project from its delivery location. Have them check the portrait and background first, then select the headline and confirm the intended family and style are available. Compare line breaks and the event date against the proof. These are proposed checks rather than a claim that a particular font package has been tested.
Close the remaining gap explicitly
Accept the editable handoff when the recipient can access the collected artwork and the agreed typography, with line wrapping and layout intact. If fonts remain unavailable, record that limitation instead of calling the package complete. A larger ZIP does not resolve a missing license or guarantee application compatibility.
Related tasks
- Why Are Images Missing When Someone Else Opens My InDesign or Photoshop Project?
- Why Does My Print PDF Show the Wrong Font or Empty Character Boxes?
- Why Does My Artwork Package Work Here but Fail on the Recipient’s File Path?
Sources and scope
- Resource Manager: Collect gathers selected linked resources; fonts are not included; Save As can be used for a separate shared document.
Primary facts come from the linked Affinity Photo 2 help pages, read directly through the web tool on 2026-10-23. Examples and acceptance checks are proposed editorial procedures, not reported hands-on tests. No market-frequency or AI-citation-frequency measurement.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.