Search the Community
Showing results for tags 'Export'.
-
Hello! I am having issues with Affinity Designer not exporting the crop marks properly on a booklet I'm trying to send to print. The bleeds are not working properly. Each finished page is 7" x 10" and I am trying to export bleeds and crop marks at .125" around each edge. I tried transforming each page to 7.25 x 10.25 thinking maybe I had to take account of the bleeds in the page size, but that didn't seem to work either. I made sure to 'include bleeds' when exporting. I am on a tight timeline to send to print and I am unable to fix this myself. Is anyone able to help? -
Hi, I am currently working on an A4 sized document and the printer has gven me precise specifications on how the need the pages. They a very specific page size of 226.6 x 311.4 mm (total size including bleed and crop marks). The export with crop marks from Publisher is a bit larger, so I could crop it if I had Acrobat — ideally though, I would like to set this page size as export size so I don‘t have to edit the exported PDF. Any idea on how to set this up? P.S. — Please don‘t try to convince me that the page size doesn‘t matter as long as the content is centered and crop marks fit. The printer insists on getting pages of this exact size and there is nothing I can do about it. -
SInce I switched to Publisher for all my CMYK work, I thought it might be time to do the same with a project using two spot colors. But I can't find a useful way to work with it. When using overprint properties Indesign makes it possible to do that per object (line or fill). I think it would be ok, to do it upside down, like the user guide of Publisher is promoting. That would mean to make a copy of a color swatch (one overprintig, one knocking out) and to use these on all objects as one wishes. And it does even work when outputing a PDF. But there is one thing missing - a preview of how my layout actually looks when overprinting, simple WYSIWYG (I'm not even speaking about a separation preview). So that is not very useful. With CMYK colors it's quite easy - you can just use layer modes (multiply) - see, what you are doing and even get it exported in a controlled way, when using the right PDF export settings. But with spot colors I didn't get any of these exported, they always change to CMYK. I've tried all possible ways (my document is CMYK, FOGRA39 and exporting as X4, X3 or other variants didn't help; of course honour spot colors is on). Any ideas? Has anybody a real workflow for that? Thanks for any help!! -
so I know that I cannot export as indd or idml but I want to export to a file format that will open on adobe indesign because I am in a team and they all use indesign so are there any free software that will convert affinity publisher files to indesign files were they can edit it. or can I use one of the file formats to export it. -
OK, here's the deal. Whenever I "place" anything created outside Affinity Publisher into Affinity Publisher, and then export the publication to PDF for CMYK printing, APub changes the CMYK values in the placed file! I have tried placing PDF files and Affinity Designer files, always the same result. I have tried every setting I can think of under preferences and PDF export that I can find. I don't want this! Why does it do this? I want to stay with APub, but this issue has me and our publishing company back with InDesign. I export to PDF from Designer, color values remain correct. I import the same file to APub, then export the page to PDF, the color values have changed! This is especially vexing with 100% black, which ALWAYS gets changed to a combination of CMYK values. My printer can't work with this. However, if I fill a square with 100% black in APub, then export to PDF, the color value remains 100% black. Argh! But, if I import a PDF or a native Designer file, then export the page to PDF from APub, I get a mix of CMYK values instead of 100% black. Argh again! This CANNOT be right. There HAS to be a simple switch fix for this. Surely SOMEBODY out there has solved this. Please help! Thank you in advance. -
Hello everyone, I have a problem with Affinity Publisher’s PDF export that makes it virtually impossible to generate print-ready PDFs. The images in my exported PDFs often—though not always—appear “glitched”, with distorted or black bars appearing mostly in the upper half of the image. I have included a comparison screenshot that shows you the faulty result of the PDF export vs. how it should look like. I have also attached both the faulty and correct PDF. I do not know exactly what causes this problem to happen, but here is everything you might need to know about it: I only encounter this problem on my Macbook Pro (2021) with M1 Max. When I export the same document through Intel-based Macs or Windows machines, the problem does not occur. I’m running the latest version of macOS and Publisher 2.2.1. However, I’ve had this problem ever since I got this Macbook in late 2021, meaning this problem also existed in Publisher 1.x (I finally got around to posting this here 🫠) Not all images are affected. On some documents, none are affected at all. I played around with the PDF export settings quite a bit and different settings do lead to different results. Exporting a PDF for screens, for example, made the problem go away … but only on one document that I tested. Weird. My guess would be that this problem is caused by PDFlib, which to my understanding is the library used by Publisher to generate PDFs on macOS. Maybe there is a bug related to PDFlib on certain Apple Silicon machines? Though the problem might be something completely different and this may just be a shot in the dark. Any help on this is greatly appreciated! Right now, I have to export any PDF that I need to have printed through my secondary Windows machine, which is obviously far from ideal. Thank you, Niklas correct.pdf faulty.pdf
-
Hi, when exporting an artboard to PNG I get an image with an unwanted white border all around. The margins are 0 in the document setup but I didn't find a way to get rid of that border. Thanks for any help -
I am trying to export a project in Affinity Publsher and everything looks fine, also when I share it to Books in order to proofread, but now I wanted to save it in order to send it to the publisher, but then I checked the preview and just one detail looks very wrong. The words come out completely illegible - it should read “collected works” but as you can see it’s just like a big blob. I’ve tried deleting it and using other fonts etc, but to no avail.
-
Since the last days I am losing all my printing (directly to my L14150 EPSON printer or "Windows Print to PDF"). All imagens with transparence backgraound started to lose the transparence or bright changing, as shown below: There is no filter, transformation, FX, mask (...) applied. Just a PNG over other image. Everything was working fine untill few days ago. What is happening? If I do the same art using Corel, the correct result os obtained: I am using Affinity V 2.0.4 and tryed to chance de color profile several times. Its an Affinity bug, definitely. Is anyone having the same bug?
-
Hello everyone, new to the forum here (long-time follower). I've been using Affinity apps since the 1.0 version and just want to say they are great products! Anyhow, I'm writing here because for the last few days I'm having some hard issues with Designer (and other Affinity apps) regarding saving documents. I the next section I will outline the problem and steps that I took to try and combat it. Also, I will attach a screenshot of the error message. BASIC SYSTEM SPEC: OS: Windows 11 21H2 OS Build: 22000.376 CPU: AMD Ryzen 9 5900X GPU: Nvidia GTX 1080 RAM: 32.0 GB Affinity Designer Build: 1.10.4.1198 Affinity Designer Beta Build: 1.10.5.1227 *note: Photo and Publisher are also the latest versions with the same problem *note: Affinity programs are installed in their default location on the computer (C:\Program Files\Affinity\) *note: all work is done on internal NVMe SSDs, SATA SSDs, and HDDs PROBLEM: Cannot save any kind of .afdesign document. Export is working fine. STEPS: 1. Open new document inside Affinity Designer 2. Go to File>Save/Save As and pick a directory to save the file 3. Error message pops out saying: "Failed to save document: <Untitled>. Save failed because access to the file was lost" (4.) Rename the file to something like "test" and the same message appears 5. There is an empty file created in the chosen location TEST SOLUTIONS: 1. Tried to downgrade the program version to 1.09 and still have the same problem 2. Turned off File>Save History with Document 3. Turned off Hardware Acceleration 4. Tried to edit a document and then save it, still not working 5. Tried to save on 4 different locations (2 SSDs and 1 HDD with 2 partitions) 6. Tried different programs (like Blender, Word, etc.) and they all work fine 7. Disabled Windows Defender (there is no other antivirus or similar programs on the PC) 8. Checked for protected folders (there aren't any) DETAILS: When trying to save a document it says: "Failed to save document: <Untitled>". After giving the document some random name, error messages still say: "Failed to save document: <Untitled>". When trying to send the file to another Affinity application (like Photo) via File>Edit in Photo... another error pops up: "Failed to launch Photo. Could not hand over the file to another application". I think that is all. I hope this information will be helpful. If there is more information or tests I could do, please let me know.
-
Can we please get export grid as an option? Currently there isn’t a way that I know of to export the grid so that it’s visible in the result -
I've had this issue many times in recent months. Here's my workflow. 1. Copy an existing document and rename it, both in Finder. 2. Edit the contents and save. 3. Export to "PDF Print" This gets me a 3 page PDF file — exactly what I expect. 4. Close the document. A short time later, after some proofreading of the PDF... 5. Re-open the document. 6. Make a minor edit and save. 7. Export to "PDF Print" I now get a 1 page PDF. I cannot make it output all 3 pages. The document comprises of: Page 1: Native Publisher content — multiple text frames and tables with text and some small images. All the images are embedded. Page 2: An embedded page from another Publisher 2 document. Page 3: Another embedded page from the same Publisher 2 document. While recreating the steps for this forum post, I discovered how to get it working again. 8. Select the last page. 9. Export "Current page". 10. Export "All pages". That final export does include all 3 pages. I have changed nothing about the document since step 6 so I know it's not me! -
I am often loading and editing SVG files in Affinity Designer for Mac. It offers excellent tools. However, I need to export to .ICO format. The ICO format is an essential image format in Windows containing several pixel frames. Currently, I export the SVG to individual PNG images (16x16, 32x32, 48x48, 64x64, etc.) and then convert/combine these PNG images to ICO in Axialis IconWorkShop. This is a lengthy, cumbersome, and time-consuming process. It would be very convenient if it would be possible to export from Affinity Designer directly to ICO format (of course containing a customizable set of pixel formats). -
Is it possible to batch save/export many tabs(seperate projects) as common filetypes( jpg,png,tiff...) in affinity photo? I'm opening a pdf that has many pictures inside so I seperate and edit each picture on a new tab/project. so instead of using save as command over and over again I need a better solution for this. any help?
-
Adding a simple check box in the export options to allow the grid to be exported would be a lifesaver. Right now I have to use a different tool to add grids.
-
Hello! I have a problem exporting my document. This is how a test (reproducing the problem) looks like: but it does not export one of the artboards: It does not matter if I want to export to PDF, PNG, ... Apologies in advance if I am doing something terribly wrong (my first time using Affinity Designer) & please help (as for now I cannot export the document I spent a few hours designing...) Thanks a lot in advance! export_problem.afdesign
-
Hello forum members, I'm facing a challenge while working on my game character, which I design in Affinity Designer and then import into Spine using the Spine JSON export settings. My problem is that I don't know how to set the origin correctly. To explain in more detail: I have numerous artboards in my Affinity Designer project. When I export my character and paste it into Spine, I have to manually move it to coordinates 0.0. Not only is this step time-consuming, but it can also be inaccurate. In the YouTube video I linked you can see how the origin is set in Photoshop so that the sprites are shown in the correct place when exported I would be extremely grateful for any suggestions for solutions and tips on how I can optimize this process. Additionally, if you have general recommendations for the Affinity Designer to Spine workflow, please share them with me. Many thanks in advance! Best regards, Trilex -
Affinity Photo v.2 have a bug where you can't create LUTs to be used for color correction in other softwares. I show here how it is not working but also that it works great in version 1 of Affinity Photo. This problem have been since December 2022 as I can see on the forum and still haven't been fixed.
-
While making textures intended for a game engine I discovered a weird issue: when I export TGA files for some reason their bottom right corner pixel gets inverted. If I export the same image to PNG or JPG there are no issues at all. I'm attaching original .afphoto file as well as TGA and an upscaled PNG file converted from TGA for better view. To reproduce this bug simply create a project and export it as TGA. You should notice exactly one pixel being inverted in the bottom right corner. I'm using Affinity Photo 1.8.5.703 T_ConcreteWall06.afphoto T_ConcreteWall06.tga
-
First: Affinit Designer is really great - thanks to the Affinity team! (Former-time Corel user, then Inkscape, now switched to Affinity due to CMYK and better color management) My request: I often use Save-As to generate numbered versions of files (as backups, and so that when I discuss them with a client, we can refer to which version we are talking about). In the Save As dialog, it appears that AD defaults to the folder where I last saved anything. This is very tricky when working on files that lie in different folders. To me, the current behaviour is somehow unexpected, and I often accidentially store files in the wrong project's folder. The same happens when exporting, to PDF for instance. I can imagine that people might want to always export all PDFs to a certain folder no matter where the curent file is, so maybe we should also consider this use-case. My suggestion is: 1.) Save As: Default to the folder where the current file lies. 2.) Export (pdf etc, but also for palettes): Default to the folder where I last exported the respective file type when the current document was open. (Maybe its not a good idea to store file paths in documents (like the export paths necessary for 2.). For me, it would be ok if this only works for the last, say, 30 files I worked on, so it could be stored somewhere in the application options storage, not in the document files.) Would this cover all use-cases? Best, Philipp -
I guess this will be a topic for many Users who are collaborating with other Affinity users still on V1. I have both versions of the Affinity suite, and am a bit hesitant to edit v1-documents because of the incompatibility with v1-apps. Is there any way to somehow "save as" or "export" v2-documents from the v2-app to the v1-document-format, perhaps with a friendly warning that one might lose some new features? Otherwise this would be a weird situation, Designer can open Illustrator files from all versions (which Illustrator cannot do), but cannot export into its very own format of the predecessor... Btw: Copying from V2 and paste it into V1 seems to work, even the controls for a cog shape still works. -
I'm conscious this has been asked before but there seem to be no recent updates here in the forums. On the iPad, can we please have a meaningful default filename when exporting images? I am using Affinity on an iPad Pro, it is fully up to date. I have tried a number of methods to import my images in the first place, but the one that seems most efficient is via the iPad SD card reader which is reasonably quick (once it has built tons of thumbnails... every time), where the Photos app imports the files. My source images are RAW files, sometimes paired as RAW & JPG (Olympus OMD camera). I have seen on the earlier threads on this subject the comment that "Photos doesn't retain the filename on import." That may once have been true but certainly is not true now and hasn't been since before the last Affinity iOS update. Both FileBrowser and in Lightroom Mobile can see the exact original filenames, same as if I had imported to my laptop. Affinity has been left behind and insists on "Untitled.jpg" as the only default option, so I have to open one of those other apps up to remind myself what the exported jpg filename actually should be (if I want to be able easily to recognise later where the export came from, which I do). Terrible workflow, and gets in the way of processing a batch of photos. An enhancement would be also to add (insert, replace) other standardised filename stubs - personally I like to prefix the capture date, others might like to add an album name when working on a bunch of photos. Any chance of an update?
-
I am creating a hyperlinked pdf intended for digital use, It consists of several weeks each week has several templates that are hyperlinked within the same week, I made each week's file seperately and when I try to merge weeks, each hyperlink points to the page within the same week in which was created but when I export it all hyperlinks point to the templates of the first week. I'm using anchors, and each week have different anchor names and they are added seperately to the same file to create the merged file. I checked those hyperlinks in hyperlinks section in affinity publisher and everything is correct but whenever I try to export the file, they get messed up !! I'm honestly a little bit disappointed because I'm launching new products in my business, I have deadlines and this surprise really ruined it all, I worked with V1 before and I didn't encounter a similar issue that's why I kept working on the project without checking in in the first place and now my 3 month work is ruined. You can find attached below afpub and pdf files Operating system : Windows 11 Software : Affinity publisher 2 SUNDAY-WEEK2.afpub SUNDAY-WEEK2.pdf -
Hello, Using Publisher V2.1.1, I have encountered multiple transparency glitches that are only apparent after exporting to PDF. The two attached instances involve an FX drop shadow. My first three or so exports were fine. Then "first page glitch" happened. I added the workaround you can see in "second page glitch" and the export was fine a few times. (Client revisions: RIP). Then "second page glitch" appeared, so I added the same type of workaround for it. The longer I edited and exported the file within Publisher, the more glitches developed on export. (There was another somewhat different glitch later, but my workaround proved better than my initial technique, so I didn't bother saving that glitched version.) I've attached the working files and their corresponding PDFs. "Second page glitch" is the original file that was created in AD and then opened in AP early on. I wondered if the app switch was part of the issue (even though the glitches appeared after several successful exports in AP), so I saved a version of the file in AP. Then I undid my workaround (box of the same size with Gaussian blur applied) and reapplied the desired drop shadow FX with the same glitched result. (The client picked the colors.... </3) OS: macOS Ventura 13.5 and 13.5.1 (Updated after glitches occurred, hoping that would solve it. It did not.) hardware acceleration: on Thanks! first page glitch.afpub first page glitch.pdf second page glitch.afdesign second page glitch.pdf
-
Adding the ability to export document presets would be extremely helpful for environments that use multiple installations of Affinity apps. To clarify to what I am referring here is a pic:
