Any good editor for creating epub in 2026?

[icearch]

After looking into Calibre editor, I have to say that it's pretty similar to Sigil. Some functions differ, but not that much, the workflow are basic the same. It boils down to personal preference.

[icearch]

After looking into MSword, I found that it's styling system isn't quite same to html, even being reflowable format.

Also I didn't find clear ways to export and import stylesheet, need more research.

[DNSB]

Originally Posted by icearch

After looking into Calibre editor, I have to say that it's pretty similar to Sigil. Some functions differ, but not that much, the workflow are basic the same. It boils down to personal preference.

There are some different tools that make me use both of them. If I want to remove duplicate CSS entries, calibre has a tool for that. If I want to use saved searches, Sigil has the edge there.

[Doitsu]

Originally Posted by icearch

After looking into MSword, I found that it's styling system isn't quite same to html, even being reflowable format.

The user might like Sigil and the optional PageEdit companion app. After installing PageEdit, they'll have to set it as the default external XHTML editor in Sigil’s General Settings. Once configured, they can click the Launch External XHTML Editor button to edit their EPUB file in a WYSIWYG environment.
This might be a good solution if an external proofreader without HTML skills needs to implement some last-minute changes.

LibreOffice Writer also includes a built-in EPUB export feature. The results are generally good, though it often uses point or inch measurements instead of em-based units for styling.

[icearch]

Is there any external XML editor other than PageEdit? The fact that you can choose implying there are. Any recommendation?

[ableal]

Originally Posted by icearch

After looking into MSword, I found that it's styling system isn't quite same to html, even being reflowable format.

Also I didn't find clear ways to export and import stylesheet, need more research.

In my experience, people prefer to work from a sample/previous document or design, replacing content, rather than starting from a blank slate, however well documented.

I.e., if you provide a well designed sample document which your helpers can just modify, you don't need to import/export stylesheets ...

[icearch]

Originally Posted by ableal

In my experience, people prefer to work from a sample/previous document or design, replacing content, rather than starting from a blank slate, however well documented.

I.e., if you provide a well designed sample document which your helpers can just modify, you don't need to import/export stylesheets ...

True, I have sample file, but in epub, created in Sigil.

I think might well just teach them Sigil, it can't be that hard right?

After refining my sample file of course.

[DiapDealer]

Originally Posted by icearch

I do download pageedit, but haven't look into it deeply since I know how to code, and it's a bit unintuitive to control tag and class in pageedit, or I just didn't know better.

It's an assumption that those who need a wysiwyg editor will not be overly concerned with the "under the hood" code. Those who don't understand the underlying code well enough to create it themselves will generally need to trust what the wysiwyg programs provide. Either that, or they can tweak the code in Sigil proper after it's been generated.

[KevinH]

If you are converting straight fiction text with few images and can live with a pre-selected set of "styles" to choose from (and have $$ to spend), I have heard that both Vellum (Mac only) and Atticus (cross platform) will do an okay job creating an epub3 that fits with their set of selected styles (and will create a pdf print layout as well).

The code generated by both is less than ideal but as DNSB said, it passes epubcheck.

Basically they are text editors that import .docx files that it then converts to a fixed set of internal (user selected) styles and then generates the epub3 automatically from them. Much like an input plugin can convert a properly styled LibreOffice and Word file.

They are not code focused at all and so would require either calibre or Sigil editing to do anything custom or unique. But if you just want to handle simple fiction and do not mind selecting from a pre-set set of themes, they can and do generate a very useable epub3. The Vellum one can even let you decide among a number of different targets and provides the required css automagically.

Caveat: I have only played around with demos of both as I had no interest in parting with $200-$300 Canadian just to create an epub that I could generate myself.

[icearch]

Originally Posted by KevinH

Caveat: I have only played around with demos of both as I had no interest in parting with $200-$300 Canadian just to create an epub that I could generate myself.

Knowledge is money haha.

[ableal]

Originally Posted by icearch

True, I have sample file, but in epub, created in Sigil.

I think might well just teach them Sigil, it can't be that hard right?

After refining my sample file of course.

People are extremely resistant to instruction (but no one has the nerve to say they can´t handle a Word document), and Calibre provides an epub-to-docx conversion ... if the round-trip is acceptable, it may save you trouble.

[JSWolf]

Originally Posted by KevinH

If you are converting straight fiction text with few images and can live with a pre-selected set of "styles" to choose from (and have $$ to spend), I have heard that both Vellum (Mac only) and Atticus (cross platform) will do an okay job creating an epub3 that fits with their set of selected styles (and will create a pdf print layout as well).

I don't know about Atticus, but Vellum produces some pretty atrocious code. Stay well away from Vellum. If you want to edit Vellums's code, you'll have a job ahead of you.

I'd rather use calibre to convert the .docx to ePub and then use Sigil to convert it to ePub3 and edit the code as needed.

[phillipgessert]

What's the workflow here? Someone is prepping files for you? Because the best tool for that might be something different than e.g. some standalone software you'd like to recommend to someone building an ebook end-to-end with no coding experience.

Someone operating totally independently will almost certainly wind up using something in the Vellum / Atticus / Kindle Create slate of tools, regardless of what more ebook-savvy folks may think of the output. Someone helping you create something more bespoke will probably be better served stopping short of an actual EPUB, instead focusing on giving you an exceptionally clean and well-structured Word file that you hike over the finish line yourself. And in that scenario they’re developing a more transferable skill, which is a decent carrot in lieu of pay.

[icearch]

Originally Posted by phillipgessert

What's the workflow here? Someone is prepping files for you? Because the best tool for that might be something different than e.g. some standalone software you'd like to recommend to someone building an ebook end-to-end with no coding experience.

Someone operating totally independently will almost certainly wind up using something in the Vellum / Atticus / Kindle Create slate of tools, regardless of what more ebook-savvy folks may think of the output. Someone helping you create something more bespoke will probably be better served stopping short of an actual EPUB, instead focusing on giving you an exceptionally clean and well-structured Word file that you hike over the finish line yourself. And in that scenario they’re developing a more transferable skill, which is a decent carrot in lieu of pay.

We have lots of separate text needs to be bundled into epub. And due to lack of spare time and energy, it better be done by more people.

After looking into actual function of software, I think your suggestion is right. It better let others create epub directly, rather than fiddle with wysiwyg word processor, just another layer of complex conversion.

The project haven't start formally yet, but I think the workflow will be: others do most basic epub creating, and I will focus on fine tuning and technical support.

[icearch]

Originally Posted by ableal

People are extremely resistant to instruction (but no one has the nerve to say they can´t handle a Word document), and Calibre provides an epub-to-docx conversion ... if the round-trip is acceptable, it may save you trouble.

I tried some style defult in MSword, but Calibre convert it in to something really messy.

Final result see attachment.

html:

Spoiler:

<?xml version='1.0' encoding='utf-8'?>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
  <head>
    <title>未知</title>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
  <link rel="stylesheet" type="text/css" href="stylesheet.css"/>
<link rel="stylesheet" type="text/css" href="page_styles.css"/>
</head>
  <body class="calibre">
	<h1 class="block_" id="toc_id_1">h1h1h1h1h1h1h1</h1>
	<p class="block_1">*</p>
	<h2 class="block_2" id="toc_id_2">h2h2h2h2h2h2h2</h2>
	<p class="block_1">*</p>
	<p class="block_3">hmhmhmhm</p>
	<p class="block_1">*</p>
	<p class="block_4">hqhqhqhqhq</p>
	<p class="block_1">*</p>
	<p class="block_5">hbhbhbhbhbh</p>
	<p class="block_1">*</p>
	<p class="block_1">*</p>
	<p class="block_6">ppppppp</p>
	<p class="block_6">ppppppp</p>
	<p class="block_1">*</p>
	<p class="block_6">nsnsnsnsnsns</p>
	<p class="block_6">nsnsnsnsns</p>
	<p class="block_6">nsnsnsnsns</p>
	<p class="block_1">*</p>
	<p class="block_7">lililili</p>
	<p class="block_7">ilililili</p>
	<p class="block_7">lililili</p>
	<p class="block_1">*</p>
	<p class="block_8">preprepre</p>
	<p class="block_8">preprpre</p>
	<p class="block_9"><i class="calibre1"><span class="calibre2">pre    </span></i><i class="calibre1">pre<span class="calibre2">   </span></i><i class="calibre1">pre<span class="calibre2">   </span></i></p>
	<p class="block_1">*</p>
	<p class="block_1">*</p>
	<p class="block_10">111111111</p>
	<p class="block_11">2222222222</p>
	<p class="block_12">3333333</p>
	<p class="block_13">4444444</p>
	<p class="block_14">5555555555</p>
	<p class="block_15">6666666</p>
	<p class="block_16">777777777</p>
	<p class="block_6">88888888</p>

</body></html>

css:

Spoiler:

.block_ {
  color: #2E74B5;
  display: block;
  font-family: "等线 Light", serif;
  font-size: 2em;
  font-weight: normal;
  line-height: 1.2;
  page-break-after: avoid;
  page-break-inside: avoid;
  text-align: justify;
  margin: 24pt 0 4pt;
  padding: 0;
}
.block_1 {
  display: block;
  font-family: serif;
  font-size: 1em;
  text-align: justify;
  margin: 0;
  padding: 0;
}
.block_2 {
  color: #2E74B5;
  display: block;
  font-family: "等线 Light", serif;
  font-size: 1.66667em;
  font-weight: normal;
  line-height: 1.2;
  page-break-after: avoid;
  page-break-inside: avoid;
  text-align: justify;
  margin: 8pt 0 4pt;
  padding: 0;
}
.block_3 {
  display: block;
  font-family: "等线 Light", serif;
  font-size: 2em;
  letter-spacing: -0.5pt;
  line-height: 1.2;
  text-align: center;
  margin: 0 0 4pt;
  padding: 0;
}
.block_4 {
  color: #595959;
  display: block;
  font-family: "等线 Light", serif;
  font-size: 1.41667em;
  letter-spacing: 0.75pt;
  line-height: 1.2;
  text-align: center;
  margin: 0 0 8pt;
  padding: 0;
}
.block_5 {
  display: block;
  font-style: italic;
  font-weight: bold;
  letter-spacing: 0.25pt;
  text-align: justify;
  margin: 0;
  padding: 0;
}
.block_6 {
  display: block;
  text-align: justify;
  margin: 0;
  padding: 0;
}
.block_7 {
  display: block;
  text-align: justify;
  margin: 0 0 0 36pt;
  padding: 0;
}
.block_8 {
  color: #404040;
  display: block;
  font-style: italic;
  text-align: center;
  margin: 8pt 0;
  padding: 0;
}
.block_9 {
  color: #404040;
  display: block;
  text-align: center;
  margin: 8pt 0;
  padding: 0;
}
.block_10 {
  color: #404040;
  display: block;
  font-style: italic;
  text-align: justify;
  margin: 0;
  padding: 0;
}
.block_11 {
  display: block;
  font-style: italic;
  text-align: justify;
  margin: 0;
  padding: 0;
}
.block_12 {
  color: #2E74B5;
  display: block;
  font-style: italic;
  text-align: justify;
  margin: 0;
  padding: 0;
}
.block_13 {
  display: block;
  font-weight: bold;
  text-align: justify;
  margin: 0;
  padding: 0;
}
.block_14 {
  color: #2E74B5;
  display: block;
  font-style: italic;
  text-align: center;
  margin: 18pt 43.2pt;
  padding: 10pt 0;
  border-top: #2E74B5 solid 1pt;
  border-bottom: #2E74B5 solid 1pt;
}
.block_15 {
  color: #5A5A5A;
  display: block;
  font-variant: small-caps;
  text-align: justify;
  margin: 0;
  padding: 0;
}
.block_16 {
  color: #2E74B5;
  display: block;
  font-variant: small-caps;
  font-weight: bold;
  letter-spacing: 0.25pt;
  text-align: justify;
  margin: 0;
  padding: 0;
}
.calibre {
  display: block;
  font-family: "DengXian", serif;
  font-size: 1em;
  padding-left: 0;
  padding-right: 0;
  margin: 0 5pt;
}
.calibre1 {
  font-style: italic;
}
.calibre2 {
  white-space: pre-wrap;
}

I have no idea what's going on here. Maybe beacuse the defult style in MSword is too fancy and messy, or maybe it's because something wrong in conversion that need to be addressed in Calibre?