View Single Post
Old 06-25-2019, 05:01 PM   #23
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 35,513
Karma: 145557716
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Tex2002ans View Post
You should be able to safely stick with 1200px width, so depending on the ratio of your cover:

1.4 = 1200 x 1680
1.5 = 1200 x 1800
1.6 = 1200 x 1920
Newer devices should be more powerful, and 1600px is a "recommended minimum", so:

1.4 = 1600 x 2240
1.5 = 1600 x 2400
1.6 = 1600 x 2560
My personal preferences are 1500x1000 (3:2) or 1500x1125 (4:3). Larger images tend to give me an epub file where the text takes <300K and the cover image is >500K. I'd rather have the smaller cover image and file size.

If the ebook looks good in ADE and/or RMSDK, with the epub3 renderer on my Kobo and with Kindle Previewer, that's as far as I go. The few times that I wasted hours trying to make an ebook look good on multiple renderers were pretty much exactly that: wasted hours. This renderer doesn't center text unless it is wrapped in a centered div, this one doesn't won't scale the image in a graphic scene break, this one tosses out the CSS embedded in the ebook and uses it's own builtin CSS, this one makes any dropcaps look like crapcaps, etc.
DNSB is offline   Reply With Quote