Unfortunately, no software will be able to keep your choice of fonts for your Kindle ebook. Kindle e-readers have fonts of their own already installed, and whatever font you use will be converted to one of its own fonts. There's no way around it. The only medium allowing you full control of the font you choose is the print version.

With print books, you have absolute freedom to use whatever fonts you fancy, provided they're either labeled "free for commercial use" or if you purchase a license specifically for desktop publishing which normally allows commercial use for print books. And don't forget to embed them, of course, although KDP does a pretty good job embedding fonts for you (but only for paperbacks and hardcovers, never for ebooks).

Answering your question, I never use Times New Roman. I much prefer Bookman Old Style because it's so much easier on the eye, probably the most readable font around, and it's only $39.90. But then again, it's only for print books... no font choice for Kindle ebooks...

 

I do not want to use my own fonts for creating ebooks per se. I just do not want to get into trouble designing an ebook and publishing it with the fonts they gave me. Especially since I am designing the ebook (with Kindle Create) using Amazon software, yet NOT publishing it at Amazon. The Times New Roman was just an example to show that a font so typically used, is actually licensed. Not that I am using it myself commercially.

 

• Do you guys use fonts you have purchased? - free fonts may be resold by scammers (and commercial fonts may wrongfully be advertised as free to use)
• The fonts that came with windows? - as far as I know, some windows fonts may not be used commercially (eg. times new roman)
• Your adobe software? - it is unclear to me when one is allowed to use Adobe fonts commercially
• other?

I use Calisto MT, which I bought a licence for. Or Minion Pro, which I can use since I own/licence Adobe software which grants me the right to use their fonts commercially. If you don't own/licence any Adobe software, you need to buy the font via Fontspring, IIRC.

As far as Windows bundled fonts go, you can use them commercially--if you have a Pro version of Windows. If you have Student or Home, you aren't legally free to use those fonts commercially.

Stay away from dodgy font sites, and you'll be safe as far as free fonts go.

 

Thank you. This is a very useful post. Fortunately I own some Adobe software, which will make some things easier for me regarding fonts I used.

Do you know how I should handle things regarding the software I am using to create my ebook? The Amazon software only has 3 fonts in them.
(I will not be distributing books with Amazon...so I am guessing my clients will not be using Kindle devices which has these same fonts installed?)

 

“Monospace” is a generic font classification like serif or sans-serif. I’m sure there are font files by that name, but more likely any software using it is just telling the reading system to use its built-in default for monospace type. It’s usually used for code.

Desktop font licenses nearly always allow for use in commercial printed materials. It’s mostly fonts obtained via free font sites that carve out restrictions for commercial vs personal use. Fonts that came to you via your OS should be fine for paperback.

Ebook is different, because the only way to embed the font is to include the actual font file within the epub itself. Thus the license to do so can be pricy, and it’s not included with an ordinary desktop license.

Amazon has traditionally disallowed use of their software (aka "Publishing Tools") to generate files meant for sale elsewhere. But I wasn't able to find the EULA for KC, so can't confirm whether that applies.

I would read that font license like this. It's meant for internal use, and Amazon developers can use it without fees or attribution to create Amazon products such as the Kindle Create application. That's pretty much it, it doesn't expressly grant you permission to redistribute it via an EPUB embed, so I wouldn't assume that's permitted. It's possible though that KC obfuscates/scrambles the font in the generated epub, which would mean you aren't redistributing it.

If you’re worried about problems in using Amazon resources to publish outside of Amazon, I think the easiest solution would be to instead use tools that are platform-agnostic. The closest free option that's comparable to KC might be Reedsy's free formatting tool.

 

“Monospace” is a generic font classification like serif or sans-serif. I’m sure there are font files by that name, but more likely any software using it is just telling the reading system to use its built-in default for monospace type. It’s usually used for code.

Desktop font licenses nearly always allow for use in commercial printed materials. It’s mostly fonts obtained via free font sites that carve out restrictions for commercial vs personal use. Fonts that came to you via your OS should be fine for paperback.

Ebook is different, because the only way to embed the font is to include the actual font file within the epub itself. Thus the license to do so can be pricy, and it’s not included with an ordinary desktop license.

I may have replied to this post, but it seems everything I typed as a reply has gone missing.

I will try again. I normally check that I use fonts that are commercially free to use. I never did so for reflowable ebooks though. I will be more vigilant from now on. I wonder why Amazon included monospace as one of the three only options to use.

Amazon has traditionally disallowed use of their software (aka "Publishing Tools") to generate files meant for sale elsewhere. But I wasn't able to find the EULA for KC, so can't confirm whether that applies.

I have gone into the software folder looking for their "terms of use" which seems to be a replica of this link. (It seems quite outdated 2012)

Amazon.com: Feature Doc 70

Online shopping from a great selection at Feature Doc 70 Store.

www.amazon.com

I would read that font license like this. It's meant for internal use, and Amazon developers can use it without fees or attribution to create Amazon products such as the Kindle Create application. That's pretty much it, it doesn't expressly grant you permission to redistribute it via an EPUB embed, so I wouldn't assume that's permitted. It's possible though that KC obfuscates/scrambles the font in the generated epub, which would mean you aren't redistributing it.

Thank you for taking the time to read the font policy, I appreciate it.

I checked the code of the exported .epub using Calibre and it definitely still sees "Amazon Ember" in the code. Heck knows what other code Amazon embeds inside the exported files like perhaps IP addresses and so forth.

If you’re worried about problems in using Amazon resources to publish outside of Amazon, I think the easiest solution would be to instead use tools that are platform-agnostic. The closest free option that's comparable to KC might be Reedsy's free formatting tool.

I wasn't worried, but I am sure as heck worried now. I have never heard of the Reedsy tool. Thank you for that and will check it out.

 

If you're asking about Bookerly, you can't get around the outline loophole because the typeface itself is proprietary and built into the Kindle devices, not inserted into the ebooks delivered to Kindle devices.

If you're looking for a good open source typeface for e-ink devices to embed in your epubs, check out League of Moveable Type's website. Barry Schwartz designed Linden Hill to be used in e-ink devices. It's similar to Bookerly without being a knock-off.

 

My issue is not as much as to which font I can use, it's a matter of getting it to work. I have tried changing the font using Calibre. It works, but the book then becomes ugly and broken in other areas. I would like to have kept the book 100% the same and just swop the font out. Calibre sure ain't easy to use.

 

Found this, but like everything on the internet, it would need checking out.

Is Bookerly Font Free?
Yes! The Bookerly font is free to use for personal and commercial purposes. Feel free to download Bookerly font family right now:

The Bookerly Font: Free Download - Onedesblog

Bookerly is a serif typeface designed by Dalton Maag as an exclusive font for reading on Amazon's Kindle devices and apps. Combined with a new typesetting engine, Amazon.com asserts that the font helps the user "read faster with less eyestrain." The font includes ligatures and kerning pairs.

All I know for definite is that whatever font you use at upload, when converted, Bookerly is the default font for reading on kindles for re-flowable text, but the reader can change to other standard fonts included on the device.

If what it says above is correct about free commercial use, then I can't see why you couldn't use the output ePub from Kindle create through other avenues. But then I could be wrong?

Please feel free to refute any of this as I am no expert on font copyright. All I do is use Word professional, and so I can use the fonts for commercial use and I use Microsoft Office and Word to format all my books' internal text and to produce ads.

 

Thank you for the research. I designed the book in "Amazon Ember" even though "Bookerly" and "Monospace" are the only other two options. Bookerly would be a better font to use than monospace, although I think Amazon may arguably detect it easier.

I now regret ever using the Kindle Create software...

 

Bookerly is not free for personal and commercial use. It is a proprietary typeface. You can download it from Amazon along with the license, which I'm sure no one who is flouting it as free has read because if they did they would realize it's not licensed for commercial or personal purposes, In fact, it's not even a license. It's an internal document explaining how Amazon owns the copyright and how and when the two proprietary typefaces should be used.

Iconography and Typography

developer.amazon.com

Just because something can be downloaded doesn't mean it comes with a commercial license. Especially when it comes to fonts, which are their own special beast under US Copyright law. If you aren't developing something for Amazon, it's best to stay away from both Ember and Bookerly. Foundries have started going after authors for using unlicensed typefaces on covers (and even with content). I'm not sure I'd want Amazon delivering takedowns to other distributors. It's just not worth the risk of poking Amazon when there are actual open source license available that allow the font files to be embedded and can be used for commercial purposes.

 

Thank you for the feedback

Just to be clear. I did not download the font. I am creating an ebook with Amazon software that has the font already inside. I am then exporting it as an .epub. I would assume this is 100% fine as long as my books are at Amazon.

I guess I will be forced to either use the ugly as heck monospace font they provide and hope clients do not mind.

 

Honestly, at this point just use D2D's epub generator. It's free to use and they rely on open-sourced typefaces that are fine for distribution.

The problem you're having right now is Calibre is not an epub editor. It is capable of doing some things, but it was never designed to generate epubs, despite what self-publishers claim. It's a simple tool and doesn't require much technical know-how, so it's recommended.

What you want to be doing is opening the epub up in Sigil. Open the CSS. Then look for the font settings. Make sure the font-family is set to serif or sans serif and let the device pick the default typeface.

 

I downloaded Sigil and will see how it works. Sounds complicated though as you are mentioning CSS which is greek to me.

I am wondering though what would happen by the time I upload my "Amazon embedded fonts .epub" in D2D's generator. Would be great if they just kinda convert it.

 

Why has no one yet said that in an ebook, the font is often determined by the user (aka the reader) on their devices and any attempts to manipulate it should be strongly discouraged, because it causes stuff to break.

Basically, if you make an ebook, you don't specify the font. Just don't. The readers and their devices do that. You want your ebook to be as break-proof possible.

 

You are right that authors shouldn't try to force their choice of font on an ebook reader by embedding the fonts.

I said this in my post which you might have missed.

"All I know for definite is that whatever font you use at upload, when converted, Bookerly is the default font for reading on kindles for re-flowable text, but the reader can change to other standard fonts included on the device.".

 

Well, first of all, you have a problem using Kindle Create and thinking you can publish that file anywhere else. It just won't happen. KC is a proprietary program and can only be published through KDP.

So, go back to Word, or one of the free equivalents. Using TNR is included in the Word software, so no issue there. For ebooks, it's all you need. So, you don't need to be worried about any of this, you are making it far too complicated for what it is.

Now, print books? Yeah. A bit more formatting, and again, can't be done using Kindle Create anywhere but Amazon.

 

I tried kindle create a while ago, and it just didn't work for me for how I wanted my ebooks or print books formatting, especially if I had the odd image, though it could have improved since then. It didn't seem to me I had any control on the outcome and from what the OP says the same is true now with the fonts, which on the face of it appears to restrict the output for use on Amazon only.

I know there are other programs for converting to ebooks and print books, some that are automated and have excellent outcomes, but they are expensive to buy. As I have Word anyway, I use that as it costs me nothing, other than the print books take some effort.

I've always formatted eBooks and print books using Word and though it might be a learning curve, there are plenty of how to free posts on blogs, books, and YouTube videos to guide you. I now have my own templates that I use to write the WIPs, so they are good to go as eBooks when complete and edited as they are already formatted to spec. It's only a question of then using my template for the print books to trans the text to the print template. For the eBooks I use TNR point 12 for the body text, and Garamond point 12 for the body text in print books.

I upload the eBooks as a Word Doc, and convert the Word doc for the print books to a PDF from Word's PDF conversion

Not sure why anyone would want to upload an epub for the ebook unless someone could enlighten me. I agree about not using Caliber for converting to epubs for upload, but I have used it for advance copies to send to readers after testing the epub to industry standards. Not had to do that for years now.
.

 

First, fonts are intellectual property and copyrighted. The fonts used by Amazon are in-house and the license to use them is part of the package. Ebooks are known as "reflowable" publications because the layout is determined by the device and the reader, who can choose font size and type, so you cannot set your font outside of the ones available. This is because the fonts must have the ability to reflow. Now, there is a setting in Kindle Create that allows you to override the font for things like chapter titles or even passages, but you are still limited to the fonts in the program.

I put together a tutorial on how to use Kindle Create to put together your book over on youtube.Currently you can use Kindle Create to make an epub version, but it will not produce a PDF file for print. The file format Amazon uses is KPF (Kindle Print File), and is used to create both the electronic and print version of the book. If you're interested in learning about how to use Kindle Create to design your book, you can check out my tutorial. I've also put together a tutorial on how to do a layout for print publication using Scribus, an open source design and layout program similar to Adobe In Line.

 

First, fonts are intellectual property and copyrighted. The fonts used by Amazon are in-house and the license to use them is part of the package. Ebooks are known as "reflowable" publications because the layout is determined by the device and the reader, who can choose font size and type, so you cannot set your font outside of the ones available. This is because the fonts must have the ability to reflow. Now, there is a setting in Kindle Create that allows you to override the font for things like chapter titles or even passages, but you are still limited to the fonts in the program.

Hi there

I am basically familiar on how to use Kindle Create. I am trying to find out the terms of using their software and fonts to create a .epub. Do they have some sort of legal standing in me using their software with the fonts inside? Am I only allowed to distribute the .epub I created with their software to Amazon?

I put together a tutorial on how to use Kindle Create to put together your book over on youtube.Currently you can use Kindle Create to make an epub version, but it will not produce a PDF file for print. The file format Amazon uses is KPF (Kindle Print File), and is used to create both the electronic and print version of the book. If you're interested in learning about how to use Kindle Create to design your book, you can check out my tutorial. I've also put together a tutorial on how to do a layout for print publication using Scribus, an open source design and layout program similar to Adobe In Line.

Thank you. Checking out your tutorial.
Edit: I like your voice. You should be on Focus on the Family or Radio or something.

 

Since I started this topic regarding the Kindle Create Amazon fonts, I went through some of my paperbacks just to double check. I see that I generally tried to use "free for commercial use" fonts as I pre-emptively tried to be as safe as possible. But I did not bother to check the licensing of very common fonts such as Arial Narrow and Verdana Bold. It is the Microsoft fonts in particular that is catching me off guard with the terms for commercial use for paperbacks especially. I had to literally change my whole document which had parts of the Verdana in.

I also own some older Adobe software and try to use their fonts where I can. It is also rather confusing as to who actually publishes the correct licensing of a font. Some places say Verdana is free for commercial use. Others will say that you have to buy it. Microsoft is the most ridiculous with their very vague wording.

I am making snapshots of the licencing of where I got the supposedly free fonts. Not sure how much that would help me. I highly doubt that someone will look at my books and complain about the fonts. It is rather the distribution channels (etc. D2D or Ingram) that have issues of the fonts I embedded in my files. Surely they can only assume I have the legal rights to those fonts?

 

Sigil does require coding.

 

Thank you.

 

D2D stipulates that they strip out fonts when you upload epubs with them:

If I format my file myself, will it look exactly the same when you convert it?

No. Ebooks are a reflowable format that allows the reader a lot of flexibility in how they consume content. To provide the best reader experience, Draft2Digital’s automated conversion process will strip out things that force formatting to be one exact way— embedded fonts, extra line breaks, empty pages, footnotes, or anything the system considers unnecessary to the final file.

Has anyone experienced that this is indeed the case?

Why I'm asking, is that if they actually strip out embedded fonts, I will not have the problem of unwanted licensed fonts in my file...Also, I would like it if D2D removes all traces of Amazon software in my file. Probably wishful thinking. I find it interesting however that Adobe Digital Editions doesn't want to preview my approved .epub file. I do not know if this is due to Amazon somehow restricting my file, or if the problem lies with Adobe. My file does however view in most other previewers.

 

Failing to display in ADE is a problem. Most non-Kindle devices use some form of Adobe’s engine under the hood. It’s likely that there is some style rule it doesn’t like.

It’s interesting to see that D2D’s conversion strips footnotes for being “unnecessary.” Wonder what the rationale is there.

 

It’s interesting to see that D2D’s conversion strips footnotes for being “unnecessary.” Wonder what the rationale is there.

I wonder if they mean replacing footnotes with endnotes, like they do in Kindle where all footnotes are automatically converted to endnotes.

 

Stan, I don't know where you're getting your information, but Kindle Create does not output an epub. It only outputs the proprietary Amazon format, and it can't be used anywhere else. So, all this work you are doing, all the worry you are causing yourself is for nothing.

You've been told to simply upload an ebook as epub, using a basic font like Times New Roman (TNR). Ebook users can adjust the font, so doing anything else is pointless. Don't embed, don't use the font you may want. Just more problems and you don't seem to be getting what we're saying.

Honestly, at this point it would be a lot easier on you to use Draft to Digital's free conversion service. You can use their file outputs where you wish. They do all the conversion, all the necessary embedding, all the placements of whatever. And it's free. Upload a Word file, let them do the work.

At this point, I see no further benefit to keep trying to explain stuff to you. You don't seem to listen, or to believe what any of us are telling you, so it's just wasting time. Good luck to you. Maybe you'll figure it out, or learn how to hire someone to do the work for you.

 

Stan, I don't know where you're getting your information, but Kindle Create does not output an epub. It only outputs the proprietary Amazon format, and it can't be used anywhere else. So, all this work you are doing, all the worry you are causing yourself is for nothing.

I'm sorry. But you are the one with the wrong info here. I created .epubs using Kindle Create. In the past, I could only do .kcb or .kpf. But trust me, I have the .epub files in front of me Just so you know, D2D uploaded my "proprietary Amazon format" file just fine. But that's not the question, which you do not seem to be getting.

You've been told to simply upload an ebook as epub, using a basic font like Times New Roman (TNR). Ebook users can adjust the font**, so doing anything else is pointless. Don't embed, don't use the font you may want. Just more problems and you don't seem to be getting what we're saying.

You are obviously not reading my post properly or you are not understanding. Let me say it once more. I am NOT trying to embed fonts. I am NOT trying to alter code. I am using Kindle Create software who gives me 3 fonts to choose from. These fonts are Amazon fonts. These fonts are exported in the .epub of to which I have no control over. I have spent months now using this software. There are more than 300-500 images that I meticulously had to place in the layout of this book. We're also talking about slicing as well as specific pixel sizes here for each image. I also had to spend many hours making the text appear right for each page.

Honestly, at this point it would be a lot easier on you to use Draft to Digital's free conversion service. You can use their file outputs where you wish. They do all the conversion, all the necessary embedding, all the placements of whatever. And it's free. Upload a Word file, let them do the work.

My book is not a typical "novel". Due to fixed layout and .mobi being phased out, I am forced to go .epub and reflowable. I am terrible at word and I have tried it for my book. The best software so far, is Kindle Create.

I am simply asking if I am allowed to distribute my Kindle Create (Amazon) ebook at places other than Amazon. Especially if their file contains fonts that ONLY comes from Amazon.
(**It is irrelevent what fonts the reader can change to. The question is whether D2D strips out these Amazon fonts when one uses their conversion service. Take note, I have uploaded a .epub to this service and they found no problems. But I am still yet to have a confirmation whether D2D strips out the fonts as they claim).

At this point, I see no further benefit to keep trying to explain stuff to you. You don't seem to listen, or to believe what any of us are telling you, so it's just wasting time. Good luck to you. Maybe you'll figure it out, or learn how to hire someone to do the work for you.

Please do not make claims when you yourself are outdated with your information. If you don't have the answers, simply do not answer to this thread. Also please do not drag everyone into your claim that I am not listening when you are not bothering to read my posts properly. I am telling you that I can create .epub files with Kindle Create. You are the one not listening...

Here's proof:
Pre-release features (beta); Update books prepared with Kindle Create ... Both KPF and EPUB formats support most book formatting features

 

I re-checked my file with Calibre to see what it picks up. What's interesting with this .epub, is that there seems to be NO fonts

The css code does however still mentions fonts:

.class-0-1 {
font-family : "Amazon Ember" ;
font-size : 1.85rem ;
letter-spacing : 0.25rem ;
line-height : 1.2em ;
margin-left : 10.0% ;
margin-right : 10.0% ;
margin-top : 4.8em ;
text-align : center ;
text-transform : uppercase ;
}

 

Just an update.
D2D does not strip fonts as they stipulated here:

If I format my file myself, will it look exactly the same when you convert it?
No. Ebooks are a reflowable format that allows the reader a lot of flexibility in how they consume content. To provide the best reader experience, Draft2Digital’s automated conversion process will strip out things that force formatting to be one exact way— embedded fonts, extra line breaks, empty pages, footnotes, or anything the system considers unnecessary to the final file.

I now may have to take alternative steps. I have found a way to rename all the fonts in my .epub by renaming it in the CSS code.
Kindle create is free software and the licensing as to how to use it is quite unclear. As a precautionary measure, I may rename all the font names as well as Amazon's name so that AI or algorithms does not pick it up. I must say, it's rather disappointing that D2D claim they strip embedded fonts when they do not. My .epub file still states the names of the fonts in the css. Perhaps there are not fonts, and it's only the names that appear in the code.

Perhaps then the solution for me will be to rename all the risky elements and re-save the .epub.

 

If there are no actual font files within the epub, then there are no fonts to strip. Font names in the CSS alone are not a license violation, they’re attempting to call on fonts built into the device or app. The lack of a font fallback and your earlier mention of problems with ADE are bigger issues with the file.

 

Could someone please perhaps share their opinion on the phrasing of Amazon regarding Kindle Create as stated in their FAQ:

Today, Kindle Create is for preparing books that can be published on Kindle. You cannot use Kindle Create to convert your manuscript to a book for publishing outside of Kindle.

https://www.amazon.com/Kindle-Create-FAQ/b?ie=UTF8&node=18674454011

As their terms are quite outdated and unclear, I would like to know if the above is perhaps also outdated? It could be that they were referring to their .KPF and .KCB files. In beta, there is now .epub.

"Cannot" vs. "am not allowed to" upload books outside of kindle. It may be possible that I "can". But am I allowed? In fact, I have actually previously published a book at KOBO using KC (have de-listed it now).

Also take note that I may be changing my code slightly after having used KC. Does that not technically change the legality of the usage of my .epub? (please forgive me for all the questions...I just want to be very precise before uploading ebooks again. It is not nice getting banned and I do not want the same to happen for some petty reason.)

 

Could someone please perhaps share their opinion on the phrasing of Amazon regarding Kindle Create as stated in their FAQ:

Today, Kindle Create is for preparing books that can be published on Kindle. You cannot use Kindle Create to convert your manuscript to a book for publishing outside of Kindle.

https://www.amazon.com/Kindle-Create-FAQ/b?ie=UTF8&node=18674454011

As their terms are quite outdated and unclear, I would like to know if the above is perhaps also outdated? It could be that they were referring to their .KPF and .KCB files. In beta, there is now .epub.

Honestly, at first glance, I understood their "you cannot" as "you're not allowed to". Not as "it's technically impossible".

 

Since it appears in an FAQ rather than a EULA, I would interpret it as them saying they don't support the use of KC for anything other than creating books for Kindle, and you shouldn't expect it to work outside of that platform. Which doesn't necessarily mean it doesn't work, it just means you shouldn't expect any help or improvements on Amazon's end with it. And Lady Runa's interpretation lines up with what's been Amazon's policy in the past re: tools like kindlegen and Previewer, so probably also correct.

To me it seems like a lot of hoops to jump through just to land at a result that sounds a bit subpar and unreliable, and if e.g. calibre and D2D are involved in the process, I don't see a lot of benefit in using KC as well. I imagine you've sunk a fair amount of time into KC and want to preserve the work that's already been done, but personally I'd bite the bullet and go another way with it. Doesn't seem worth the effort.

 

Thank you again for the replies

The book is about 99% complete. I know it's jumping through a lot of hoops to get there. But since I am not a coder, nor do not have money to pay for one, I will probably have to jump through many more hoops anyway. I don't mind if I do not get any support from Amazon. My only real concern is if I am legally allowed to use their software to create a book that gets uploaded elsewhere.

As for Calibre, the steps I have to take are minor. I just use Calibre to create my metadata, as well as to rename the fonts (if I am still going to do this). I only edit the code of the .epub, but do not re-export the file. I have actually created a word doc of the book and have also used Indesign to try and create .epub. I ended up having to redo the book in KC as it was just too difficult for me. I can remove the "Kindle Create" term in the code, but then it's probably about ethics.

Urgh. This is so frustrating. Sorry for all the questions.

 

So I finally completed my .epub after months of formatting. The .epub looks great in Kindle for PC as well as Kindle Previewer 2 and 3. It looks okay in Calibre and Icecream reader. Not better than what one can expect from those viewers.

- The book finally works in portrait and landscape mode (single column, 2 column and 3 columns). I did however in a disclaimer explain to my readers that reflowable books will appear differently on various devices. I also recommended a font size for tablets.

- My only problem is that due to over 300 images, the book is almost 20mb. The book also refuses to open in Adobe Digital Editions, even though D2D says the file has no errors. (EDIT: The book opens in ADE 3.0 but not 4.5.11). Kindle Previewer 3's scan also gives no errors. Pagina .epub validator also gives no errors.

- I have re-read the Amazon terms for their free software. Most of it seems like they do not want us to distrubute their software or alter the code. I struggle to find any documentation that is more specific to their .epub which only became available in the last year or so in KC beta. If .epub is universal, is it not okay for me to upload this file? I mean, D2D distributes epubs to Amazon. So surely Amazon allows epubs to be created and uploaded elsewhere? I do not see how they can provide free software and then force us to only upload to their channel when it comes to a universal filetype? Either way I may be forced to upload and hope for the best. As far as I know, Amazon can only revoke my license to use KC which is in any case free to use.

- I had to use Calibre to enter metadata as well as to add a cover. I will also be editing out any words associated with Amazon or Kindle. What is strange that when ever using Calibre for whatever reason, the code is altered that their name is always included. I also plan to edit my dc:identifier number if this is possible.

I have a question. Is it possible for Amazon epub files to act as mallware or almost a virus in that it can communicate with Amazon servers through its code? I would really like for my epub file to be standalone from Amazon. I know I sound paranoid...but it is Amazon who made me this way.

 

There are alternates to Kindle Create, which is an excellent free tool, but you are limited to their fonts and their distribution network. Though, KC now does have the ability to create EPUB files, allowing for your e-book to be more widely distributed. That said, you're still restricted to Amazon for your print editions, and there is very little formatting for these, and you face the same font restrictions. Reedsy is a very popular free resource that allows you to create both print and e-book editions, and they have a library of licensed typefaces (technically, a font is the type of imprint, such as bold or italic, while the type face is the style of letters and glyphs), but you are limited to their templates for producing your layout.

For my money, literally, I have been impressed with Atticus, which also has an extensive library of licensed typefaces. And they recently made available all of Google's typefaces, though it is in beta, and only works for print books. Further, they have customizable templates, which allow you to make your book unique and have far greater control of its layout, both for e-books and print publications.

I used to use HTML to do my e-book layouts, and Scribus (a free, open source alternative to Acrobat Pro) for my print books. It was time-consuming, and I spent hours on e-book design, only to spend even more hours doing the interior layout for my print books. Atticus gets all that done in a fraction of the time, and while it doesn't get me 100% of what I could do in Scribus, it's close enough. And the hours of time it saves me, made it worth every penny. All that alone would be worth it, but I have a large library of licensed typefaces at my disposal as well.