Scrivener 3.02: I have to admit, it was the first time I have generated a PDF out of Scrivener for print. Usually, I’m producing eBook content (ePub, mobi). Today I wanted to evaluate the possibilities to use a PDF for KDP Print. I could pretty much figure all out, except one thing: The PDF resolution. Where can I set the DPI for the exported document? 300 dpi is recommended for print, so I wanted to make sure it’s set accordingly.
Any hint would be appreciated.
I’m not sure if this is what you mean, as I’m not familiar with there being an overall DPI setting for the entire PDF (most elements of it would be vector, like fonts), but if you have embedded PDF graphics that must get converted to PNG, there is a DPI setting in the Sharing: Export preference pane, right along the top. Otherwise images use the DPI you save them as.
Thank you much for your answer.Yes, this is what I mend. I do have lots of Illustrations in my novels and was wondering how the compiler handles them when it creates a PDF. So you are saying JPGs for example just get embedded as is, there is no step in the compile process that does a “compression” or “format conversion” while processing. I saw the PDF-> PNG settings but from the translation (German) it wasn’t quite clear to me if this means the compiler is using the DPI value I’m setting, or if this is just for special cases and non supported formats (as the descriptions says).
Ah, sorry the translation is a bit confusing—but to be fair it is a slightly confusing topic as well, even for those that know a fair bit about graphic design. Well to separate out a few different threads:
- The “DPI” of an image is simple a ratio between the configured display size of the image (cm, mm, in, pt…) and however many pixels that image has stored within it. If an image has 300 pixels per inch and it is 5" wide, then that image is 1,500 pixels across.
Importantly, there really is no such thing as DPI, in the sense of there being a setting that needs to be protected or some-such. It is the result of a mathematical formula. So long as the quantity of pixels in the image does not change (which Scrivener will not do) and the display dimensions on the page do not change (which Scrivener will not do) then the “DPI” is the same.
- Consequently has nothing to do with file format or compression—so long as the file format supports the notion of storing display size of course. I believe for instance GIF does not, being designed long ago purely for digital output.
I don’t think for PDF Scrivener needs to do any processing or recompression. If it does, JPG files will convert to PNG files internally during compile, which means they get converted back to JPG. In accordance with the above, that doesn’t change anything with regards to the resolution of the image, but for highly compressed images it may incur a drop in quality. For one iteration like that it’s not going be something you’ll even notice in most cases. You would have to analysed the image at the pixel level in a tool like Photoshop to even see where the recompression impacted the image. Recompression is generally something you want to avoid, but more as a side-effect of iteration—i.e. you wouldn’t want to take the image from the PDF and put it back into Scrivener and compile again, and then repeat a dozen times. Continually recompressing from the same source file however is fine.
The DPI setting in Preferences is purely for vector graphics in Scrivener that must be converted to raster images because the output format does not support vector. It determines how many pixels per inch will be used.
[size=80]I would also add the general disclaimer that I don’t claim the macOS print driver’s PDF generator is the best place to be typesetting a final book with production ready graphics. I’m not sure how that is going to handle colour correction, profiles, CMYK, etc. This is really more meant to be a facility for proofing copies than replacing a design environment. We cannot vouch for these processes being used to create professional results.[/size]
Amber, thank you so much for your detailed answer, even on a Sunday.
I do see much clearer now and really appreciate you time and efforts.