RGB vs. CMYK for Self-Published Book Covers: Which to Use

CMYK is the norm for color printing, and IngramSpark requires it for print covers, with total ink capped at 240%. KDP accepts either CMYK or RGB, converting RGB itself. Ebook covers are RGB everywhere. The right answer to an RGB vs. CMYK book cover question depends on which platform receives the file, and on who does the converting.

What’s the Difference Between RGB and CMYK?

RGB stands for Red, Green, Blue: a way of describing color by combining emitted light, so the more light you add the closer you get to white. It is how every color screen works, from a monitor to a phone to a color e-reader, which is why files destined for screens are built in RGB. Because it works with light rather than pigment, RGB covers a very wide gamut (the full range of colors a system can show), including bright blues, purples, and electric greens that cannot be reproduced on paper at all.

CMYK stands for Cyan, Magenta, Yellow, and Key (black), the four inks used in color printing. Ink sits on paper and absorbs light rather than emitting it, so the more ink, the darker the result. Because it depends on pigment, the CMYK gamut is considerably narrower than RGB, and colors that look vivid on screen often print more muted. Each ink is specified as a percentage, and the four percentages in any one spot can be added together; that total is what a limit such as 240% caps, and it exists because paper will only absorb so much ink before it stops drying properly.

The practical consequence is that a cover designed in RGB can preview brighter than the printed result. The difference is greatest in saturated colors outside the CMYK range, which printers call out of gamut. That gap is not a fault in anyone’s file; it is the difference between light and ink. The question a cover file has to answer is only who closes the gap, and when.

Which Color Mode Does Each Print Platform Ask For?

Print-on-demand platforms handle color differently, and the two that most self-publishing authors use, Amazon KDP and IngramSpark, handle color differently at the point of upload: IngramSpark asks for CMYK, while KDP accepts either. What actually separates them is narrower than it first looks: not what they will accept, but who does the converting and when you get to see the result.

Amazon KDP does not require you to convert. Its paperback cover guidance recommends CMYK without requiring it: one line says “Images should be in CMYK color to ensure your cover looks good in print”, while its section on color spaces describes RGB, CMYK, and grayscale neutrally as ways of describing color numerically and sets no required mode. What it warns against is mixing them: “We don’t recommend using multiple color spaces in a file because it can cause color variance and unexpected results when your book is printed.” The same page says color profiles (the settings a file carries to describe how its numbers should be interpreted) are “automatically removed before publishing”, so embedding one achieves nothing. It is also candid about print-on-demand color generally: “we have acceptable levels of color tolerance”, and “most color variance happens as a result of environmental and mechanical factors.”

Either way, a KDP book is printed in CMYK: an RGB file is converted before it reaches the press, so the only question is who does the converting. Out-of-gamut colors have no close CMYK match, so they can print differently from how they look on screen whoever converts them. Sending RGB and letting KDP convert can work better, because KDP manages the specifications of its own printing equipment. A conversion you do yourself uses a profile you have chosen, since KDP names none. Either route still needs a proof, covered below.

IngramSpark asks for CMYK on print covers. Its File Creation Guide (version 8.24.26) says of a print cover file that “all images in a cover file must be CMYK”, sets the required formats as PDF/X-1a:2001 or PDF/X-3:2002 (two standardized flavors of PDF built for commercial printing), and caps total ink at 240%. Its ebook section asks for something different, covered further down. What it does with a file that arrives in RGB anyway is the part worth reading closely: “RGB files received will be converted to CMYK before printing. RGB / spot color with/without transparency may produce unexpected color results when printing.” It then says who owns the outcome: “Any dissatisfaction with color shift will be the publisher’s responsibility to correct.”

So neither platform simply refuses an RGB cover. Both convert it. The difference between converting your own file and letting the printer convert it is not whether the book prints; it is whether you have seen the converted colors before the book goes on sale. The same holds for ink density: the guide says files above 240% “may be rejected for correction”, and in the next breath that such files “may process and print without rejection”, with a corrected file required later if print problems appear.

This is why color behaves differently from the other things that can be wrong with a cover. The automated validation these platforms run tests a defined list, and a file with unembedded fonts or the wrong page size fails that list and comes back to you. A file in the wrong color space is not on the list: it goes through, gets converted, and the first sign of trouble is a printed copy that does not look like the design on screen. Our guide to fixing a rejected KDP cover file covers the faults that do stop a file.

Which Color Mode Do Ebook Covers Use?

Ebook covers are RGB, because an ebook cover is only ever displayed on a screen. Amazon’s ebook cover criteria specify a color profile of “RGB (red, green, blue)”, a TIFF or JPEG file, ideal dimensions of 2,560 pixels high by 1,600 wide, and a height-to-width ratio of at least 1.6:1. IngramSpark is equally flat in the ebook section of its File Creation Guide: “All front covers must be RGB.” Note that this is its rule for ebook covers specifically; the same document requires CMYK on print covers, and the two sit in different sections for that reason.

Within RGB, sRGB is the sensible working space. Adobe RGB and ProPhoto RGB have wider gamuts, but they assume a color-managed viewer, and reading apps and e-ink devices generally are not one. A file in a wide-gamut space shown in an application that ignores the profile will look flat, which is the opposite of what the wider gamut was for.

One thing worth knowing about file preparation: Amazon states that “we apply additional compression to images when displaying them on the website”, and asks you to “upload your images with minimal compression” for that reason. Squeezing a JPEG hard before you upload means the image is compressed twice over, and the second pass is not yours to control. The full set of dimensions and file-size limits is in our guide to ebook cover dimensions and specs.

When and How Should You Convert Between Color Modes?

The cleanest approach is not to convert a finished file at all, but to keep one master and export a separate file for each place the cover is going: one for the ebook, one for each print platform. Converting is lossy in one direction. Taking an RGB image to CMYK and back to RGB does not restore the original colors, because the CMYK step discards the values that fell outside the printable range and nothing brings them back. Leave the master untouched and export from it every time.

If you are commissioning a cover, the practical move is to tell the designer every platform you intend to publish on before they start, so they deliver the right file for each rather than converting one afterwards. A designer can also soft-proof the cover, which means previewing it on screen through the destination’s CMYK profile, and that catches the worst shifts before anything is printed.

If you are converting yourself, Adobe Photoshop and Affinity, which Canva now offers free to individuals, both handle CMYK conversion with full color-profile management. In Photoshop the route is Image > Mode > CMYK Color, choosing a print profile such as US Web Coated (SWOP) v2 for North American printing or Fogra39 for Europe; the profile is a description of a particular printing setup, and choosing one tells the software which colors are actually reachable. GIMP handles CMYK through plugins rather than as a built-in mode, so it will produce a converted file but gives you less to work with when you need to inspect the individual ink values.

Two conversion faults are worth checking for specifically, and both concern black rather than the bright colors that attract more attention. The first is small type built out of all four inks instead of black alone. On a letterform a couple of millimeters tall, the four inks have to land on top of each other precisely, and any drift shows as a soft or slightly colored edge; IngramSpark’s guide asks for “100% black only” on text at 24 pt or below.

The second is the reverse case. Across a large solid area, a black built from all four inks (a rich black) reads deeper than black ink alone, so it is the right choice there; what goes wrong is how much ink it uses. IngramSpark’s recommended rich black is 60% cyan, 40% magenta, 40% yellow and 100% black, which comes to exactly the 240% ceiling, and the rich black some design applications reach for by default sits above it. A background built on that default is over the limit before you have done anything to it.

Why Does a Physical Proof Copy Still Matter?

No color workflow removes the need for a printed copy of the finished book. What you see on screen and what comes off the printer are separated by the paper, the machine, and its ink settings, and none of those live in your file. A cover laminated matte absorbs light and reads darker and flatter than the same artwork laminated gloss; that is a property of the finish rather than of your colors, and nothing you do in Photoshop anticipates it.

A proof matters more than it might because of how the platforms handle files. IngramSpark’s guide states plainly that “files are processed as received and are not preflighted prior to processing”; preflighting, in print production, is the stage at which someone goes through a file in advance and flags what will cause trouble. What runs instead is automated validation against a set list, and color shift is not on that list. Unless you have a designer or a file-prep service looking at it, a proof copy is the first point at which anyone sees the printed colors, and you would rather that be you than a reader.

Your monitor adds a second unknown, not to the printing but to your judgment of it: if the screen has never been calibrated, you cannot tell whether a color shifted during conversion or was never the color you thought it was in the first place. A hardware calibrator sets the screen’s white point and brightness response to a known standard so that at least one end of the comparison is reliable. That is worth doing if you are preparing several books, or if color is central to the cover. For a single novel with a dark background and light type, a proof copy answers the same question more directly.

Order a proof from each platform that will print the book, not one from whichever is quicker. Different machines, papers, and tolerances give different results, so a proof from KDP tells you comparatively little about how IngramSpark will print the same file, and if you are publishing on both you want to have seen both. Our comparison of a galley, an ARC, and a proof copy explains which of these does which job.

Where color is critical to the book (a cover built around one exact shade, or an illustrated interior), one copy may not be enough to judge it. Print-on-demand copies of the same file can vary from one printing to the next, so order four to six copies across two different days to see the range a reader might receive.

The short version: RGB for every ebook cover. For print, CMYK is the norm and what IngramSpark asks for, at 240% total ink or less. KDP accepts either, and sending RGB lets KDP do the conversion for its own equipment; whichever you choose, keep to one color space in each file. Keep one master and export a separate file for each destination rather than converting one file back and forth. Then order a proof, since this is the only way to know how the color will actually print.

Frequently Asked Questions

Will IngramSpark reject my cover if I upload it in RGB?

The print-cover section of its File Creation Guide says all images in a cover file must be CMYK, but the same section also says “RGB files received will be converted to CMYK before printing”, and that such files “may produce unexpected color results”. So the likelier outcome is not a rejection but a printed cover whose colors you did not choose, with correction treated as your responsibility. Convert deliberately and you keep the decision. (Its ebook section asks for the opposite, RGB, which is why the two are easy to confuse.)

What CMYK profile should I use for KDP if I convert before uploading?

KDP names no CMYK profile to use, and its cover guidance advises against embedding color profiles at all. If you submit CMYK, US Web Coated (SWOP) v2 is a sound default for North American print-on-demand and Fogra39 is the European equivalent. Note that KDP removes embedded color profiles before publishing, so the profile guides your conversion rather than traveling with the file.

Why do my CMYK colors look duller than my RGB design on screen?

That is the conversion working as designed. The CMYK gamut is physically smaller than RGB, so saturated colors, particularly bright blues, purples, and electric greens, are clipped or remapped to the nearest printable equivalent. The printed result will match the converted CMYK preview rather than the original RGB design, which is the argument for designing with the destination gamut in view from the start.

Do ebook covers need to be CMYK if a print version exists?

No. An ebook cover is displayed on a screen, so it stays RGB whatever color mode the print edition uses. Amazon specifies RGB for Kindle covers, and the ebook section of IngramSpark’s File Creation Guide says all ebook front covers must be RGB. Export the two separately from the same master rather than reusing the print file for both.

Do all the images inside my book need to be CMYK too?

Not necessarily, and an interior follows different rules from a cover. IngramSpark asks for grayscale images in a black-and-white interior and CMYK in a color interior; KDP accepts either CMYK or RGB in a color interior and converts RGB itself. The point worth carrying across both is consistency within a single file, which is what KDP warns can otherwise cause color variance and unexpected results in print.