Jump to content
You must now use your email address to sign in [click for more info] ×

Export to PDF from AP miscolours some objects

Recommended Posts

 This is about PDF export from Affinity Publisher. Tested with AP 2.1 and AP 2.2 b6711, iPadOS 16.6, iPad Pro 12.6 (6th generation). 

I have two objects, seemingly the same colour (left). When saving as PDF (for print) (vanilla settings), one gets a wrong colour for one of the objects:

IMG_7086.thumb.jpeg.836976922dd576787884dc8d95b3d948.jpeg       IMG_7088.jpeg.63c1368dc0579ce5f12fa7281e8f5985.jpeg

I enclose the original afpub file and the exported pdf.

As this is for a soon-to-be-published book with many occurrences of this bug, I hope it will be fixed soon.

Best regards,


colourtest.pdf colourtest.afpub

Link to comment
Share on other sites

31 minutes ago, joe_l said:

If I tweak the Pressure profile of the left element a tiny bit, both colours match exactly.

Yes, the bug isn't stable. However, I want AP to be predictable here, not tweakable. Select same fill colour selects both objects, yet the left one gets miscoloured. Copy the right object, paste style on the left, still it gets miscoloured.

My current workaround fix is: Duplicate the ok object. Change corner cordinates to those of the not-ok object. Delete the not-ok object. Now the image looks the exact same in AP, and works when exported (no miscoloured objects).

Link to comment
Share on other sites

The issue appears to relate to the stroke positioning, i.e., it only seems to affect centred strokes. Changing the stroke to either outside or inside (which may not be an option) remedies the colour change on export issue...

Testing in v1.10.6 and the issue doesn't exist regardless of stroke positioning...

Affinity Designer 2.5.3 | Affinity Photo 2.5.3 | Affinity Publisher 2.5.3
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.5, Magic Mouse

Link to comment
Share on other sites

  • 8 months later...
  • Staff

The issue "Expand stroke fails on specific curve with pressure" (REF: AF-3080) has been fixed by the developers in internal build "".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

Link to comment
Share on other sites

  • 3 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.