Blades of the Fallen – Out Now

One last update: Blades of the Fallen is now available for Kindle, in all other e-formats, and in paperback.

Blades of the Fallen is a standalone novel in the NEXUS space opera series.

Blades of the Fallen Cover

The murder changes everything. The Vanguard is supposed to protect against such violence, not fall victim to it. But even the so-called ‘Fallen’ wouldn’t kill without reason. Would they?

The murderer changes everything. The Fallen keep to themselves, living comfortably separate to other Necurians. But he is dragging them towards war. Why is he so convinced that it’s the Vanguard’s fault?

The inquisitors have changed. As teenagers, they witnessed the murder in front of their eyes. Five years later, they wield the authority of the Vanguard, and they will hunt down the killer. The motives must be uncovered. Because even the Fallen would not kill without reason.

Meet a handful of the characters:

Solan | Rialen | Ailan | Mara

Newsletter and Stuff


Actually, no stuff. Just newsletter. You probably noticed when you came to the site that a pop-up asked you to subscribe to my new newsletter. I’m a little late to it, but I thought it was about time to start building up a list of people who might like to support me and who might be interested in new releases and, occasionally, whatnot.

The pop-up itself I can’t customise any more than giving it a 5-second delay, which is annoying because who’s going to know if they want to sign up within 5 seconds?

Anyway, the newsletter will be very infrequent: mostly when I have a new release or something changes with a current book, and in the rare event that I actually write multiple decent blog posts. I will also keep an eye out for other interesting news and stuff with which to fill them out. So, expect something like 2-3 per year…

If you closed the pop-up but this invigorating, rallying cry has changed your mind, there’s a link to the quick sign-up form at the top of the sidebar. Thanks for your support (not a guilt trip).

Battles of Hastings

This time around, the decision was made not to release Wyrd Worlds III, the science fiction and fantasy anthology I was a part of the first two times. Instead, several of the authors involved in those anthologies are releasing short stories to coincide with the 950th anniversary of the Battle of Hastings.

These stories are already up for pre-order, so you can make sure to have them in your collection on the day (14 October).


The Battles of Hastings, by Steph BennionWho really won the Battle of Hastings? Eighteen-year-old Jane Kennedy, a twenty-first-century Chicago girl on her first field assignment, had expected a simple mission to gently ease her into the time-bending realities of her new job. Yet here she was, lying semi-conscious amidst the wounded and dying of a particularly gruesome battle, wondering what the hell she had let herself in for. In this novella based on Jane’s memoirs, follow her strange journey through multiple realities as her fellow time travellers each realise they come from a future with a different past. Is there a rogue on the loose out to change history? The Battles Of Hastings is a romp through alternate time lines in England 1066 to mark the 950th anniversary of the invasion that shaped Britain and Europe today.





Thomas is a member of the Fyrd and is recruited into Harold Godwinson’s army to confront Duke William II of Normandy. He is befriended by a blond-haired man called Kauko as they march to war. Thomas has no time for lords, kings or gods of any kind but Kauko seems to have a large amount of time for Thomas. Why is Kauko so interested in the welfare of a farmer’s son, and just what does he intend to do with him? As the relationship develops and the pair of them confront the stupidity and darkness of war, Thomas comes to realise that they did not meet by chance. In fact, Kauko has been preparing for this for a long time.




hastings-barbNineteen-year-old Robert Malet followed William the Bastard to England to claim the English throne. The battle near the small town of Hastings is the beginning of the Norman conquest of England, but also of Robert’s second life.
A vampire in 12th century Europe traveling, fighting and meeting his siblings in darkness, changing names through the years when his mortal life is gone.
Follow Robert Malet, Brother Geoffrey, Robert Capuchon and Mercadier through the years. History and fantasy based on medieval chronicles for a Vampires Through the Centuries novella.







hastings-victoriaIt’s October 14th 1066, and King Harold’s Saxon army is about to go in to battle against Duke William’s invading Norman army. Among the ranks of the Saxons are two boys who shouldn’t be there: Eadweard, and his best friend, Cerdic.
Daydreams of becoming great war heroes had the boys convinced to disobey their Fathers and go to war, despite the possibility of punishment if they were caught. Now it’s time for the battle to begin, and Eadweard is starting to wish he’d stayed home after all. But it’s too late to turn back now, and Eadweard finds himself witnessing the events of the battle that would later be called The Battle Of Hastings, and learning how different from his imaginings the reality of war actually is.
*Note: This is a work of fiction, which is based on actual events. It tells the story of the battle between King Harold’s Saxon army and Duke William’s Norman army, which took place a short distance away from the town of Hastings on October 14th 1066, in a place now known simply as Battle. Though this is a children’s story, the recommended reading age for this book is eight years and over, since it is a story that takes place on a battlefield, and therefore contains scenes of violence that are not suitable for younger, or more sensitive, readers.






Still Alive

You might be forgiven for thinking that perhaps I had died and decided that in this new state of unliving, I would abandon my blog. This is, you will be ecstatic to hear, not the case. I have been busy with a death that doesn’t belong to me, the following despicable family behaviour, a job, a new car (it has GT on the back!), moving house, trying to get internet, and making my beta readers cry.

Yes, finally, the third book in the NEXUS series is (kind of) finished. I started writing it as soon as I finished Temple of the Sixth and set it aside time after time to write Kira, Acts of Violence, and Kira Part II, but at last the most abused book I’ve worked on is nearly ready. It still needs a bit of rewriting and then editing and proofreading, but it’s not too far off now. Hopefully.

Trip To Space

After this stop-start, stop-start, I hope at least the next two books will come quicker and smoother, but thinking about other projects is what got me into this four year crawl in the first place, so let’s ignore that for now.

So, sooner or later I’ll be posting again with a synopsis and release date…or just a cover. Or a rant about another film.

New Cover

Just a quick update to say that I have changed the cover for the ebook version of Acts of Violence to fit the new paperback version (available soon). There’s a little man and everything! Here they both are:

Acts of Violence paperback cover

Paperback Cover

Acts of Violence eBook cover

Kindle Cover

Suspending Disbelief: The Line

This is another article I wrote for Uproar Comics.

Suspend Disbelief

When it comes to films, games, and even books, we’re often expected – and required – to suspend our disbelief concerning certain things. Giant, transforming, alien robots…okay. Scientist turns into a big green monster when he gets miffed…fine. Peter Quill floats in space for a minute and survives?! Absolutely unacceptable!

That was the complaint about Guardians of the Galaxy (a year ago now) that sparked in me the question: where is the line? And why is it there? I don’t expect to be able to answer the question, or make a coherent argument with whatever it is I’m about to write, but that’s not going to stop me from diving in.

So let’s start with that complaint. Guardians of the Galaxy: a superhero film (kind of – I’d argue about that, but it’s irrelevant) about a group of criminals coming together in a distant part of the galaxy to prevent an already-powerful blue person from using an alien artefact to wipe all life from the surface of the planet Xandar. Yep, all good so far; why there’s barely any disbelief to suspend.

The aforementioned group consists of a human kidnapped by aliens as a child, an artificially enhanced green assassin, a big red angry man who takes everything literally, a bipedal talking raccoon, and a talking tree monster. All fine. Nothing untoward there.

However – and here is where the film apparently crosses that line – what GOTG seems to have drawn the most criticism for is a scene where Gamora the green assassin finds herself floating in space. Quill, the human, gets out of his ship and puts his breathing mask on her. A minute later, they’re picked up by another ship and they’re both fine.

‘How unrealistic’, people said. Unlike the talking raccoon arguing with the talking tree.

First off, let’s look at what happened in the film versus what would happen in real life.


Guardians of the Galaxy

Gamora’s ship is destroyed, leaving her floating, unconscious, in open space just outside the atmosphere of where they’ve come from. Quill, in his leather jacket and t-shirt, gets out of his own ship and floats over to her. He takes off his mask, which allows him to breathe, and puts it on her. As he watches her, his eyes and face begin to freeze over and he loses consciousness. Shortly after, they are picked up by another ship, and as they tumble into the cargo bay – or whatever – he wakes up. Seconds later, so does Gamora.


Let’s assume that Quill was a real person, floating just outside the atmosphere of Earth, without a spacesuit. What would happen to him? That’s rhetorical; I’ll tell you:

  • Ebullism – The low pressure of a vacuum means the boiling point of Quill’s body fluids drops below his body temperature, causing the formation of gas bubbles in said fluids. His blood won’t boil, but he will swell up to twice his normal size. Which will hurt.
  • Within about 15 seconds, the lack of oxygen will cause him to lose consciousness. He’d then die a couple of minutes later. If he tried to hold his breath to extend that time, that air would expand rapidly, rupturing his lungs.
  • Although it’s a touch chilly, he wouldn’t freeze to death, because the vacuum means the transfer of heat would be so slow, the lack of oxygen would get him first.
  • The sun’s UV would burn him quite unpleasantly, then it would join other things such as gamma radiation and X-rays to damage his DNA. In turn, this would cause mutations and probably cancer.
  • He would, however, have about one or two minutes to be rescued.

Going by memory alone, I think Quill is exposed to space for between thirty seconds to a minute. After removing his mask, he did indeed lose consciousness pretty quickly. So the most unrealistic part of that scene seems to be that he didn’t swell up, he didn’t burn, and he froze over. We could argue that he only froze on the surface and that this might happen (I’m not a scienceer). How fast he would swell and burn, I don’t know; perhaps it would take longer than he was actually out there.

So that leaves the DNA mutations and cancer. But where are they?

AstronautNot here, in our solar system. Are they being exposed to the same things as they would just outside Earth’s atmosphere? In the same quantities? I don’t know. Do you? Do the complainers? Would so much time travelling in space, on different planets, etc, have changed the way his body would react to things? Someone probably knows, but it’s not me. Perhaps the NASA advisor they used for the film knows.

So these people can deal with a talking raccoon (in the same universe as a god of thunder, teleporting mutants, and gargantuan ‘celestial beings’ whose skulls are used as cities floating in space), but the fact that the rest of the film after this scene didn’t deal with the tragic loss of Peter Quill to cancer is too far over the line. Interesting.

What if it was Superman in space? Would the same people be annoyed that he survives rather than dying horrifically?

The line is different for everyone, of course. My grandmother would never watch something like Guardians of the Galaxy – or indeed Superman – because they have ‘weird aliens’. There’s plenty of things I’ve watched that made me roll my eyes, though I can’t think of any now.

Beyond the Guardians

Shadow of the Wraith, Kindle coverI’ve complai…uh…mentioned before a 3-star review I’ve had on my first book. According to the review, it lost a star due to taking ‘an unexpected turn into fantasy territory’. I won’t bother mentioning the inane nature of complaining about a science-fantasy novel having fantasy elements (oops, I just did), but this is perhaps her line. When sci-fi becomes science-fantasy, she can’t suspend her disbelief any more, perhaps. Star Wars is fine until the Force comes into play. Likewise, mine was fine until telekinesis came into play. Or, as she called it, ‘use his “special powers”’. Not that I’m bitter.

And what about within the book? If someone went into it, open to the inevitable fantastic elements of a science-fantasy novel, where might their line be then? The telekinesis, telepathy, etc, that are possessed by one of my alien races? The not strictly realistic space battles? The androids? The dragons? I suspect the last one might be a line for a lot of people. Until they open book two and discover immortal ‘gods’, angels and zombies. Technically not zombies actually. But the dragons are alien animals, not creatures of myth. Does that help? It might help person A but not person B.

What about CSI? ‘Enhance!’ ‘Enhance more!’ ‘Enhance again and zoom in on that reflection in the reflection and enhance!’ Most people can’t quite suspend their disbelief enough for that, but others can. Perhaps it depends simply on how much you know – or think you know – about the subject in question.

I hope you don’t think I’m going anywhere with this, or making any kind of point. Because…I’m not. Maybe I should. But I won’t. Don’t be annoyed – I told you at the start this wasn’t going to go anywhere! It’s simply a question that can’t be answered. Not by me, anyway.

So, what’s the line for you? What was the last thing that made you roll your eyes and groan?

Kindle Direct Publishing Formatting Guide



I recently wrote a guide on writing a book, and in it I said that I would write a guide to formatting for KDP (Kindle Direct Publishing). This will be vaguely similar to my Smashwords formatting guide, but simpler.

I’ve heard of plenty of people using the simple, automated process that KDP seems to expect by default, but to be absolutely sure that no issues will arise by the conversion process, I convert my Word file into an HTML file first. Doing so means that, so long as I make sure only HTML tags that the Kindle recognises make it through, what comes out the other end of KDP will be exactly what I want. The only errors possible in this way are any made by me.

Most people think that because this is done through HTML, it is therefore over their heads and far too hard and technical. In reality, HTML is a lot easier to grasp than you probably think. More to the point, you don’t really need to know HTML; you simply need to know what HTML tags should and should not be present in your file.

What You Will Need:

  • Microsoft Word (it shouldn’t matter which version, and if you are using any other program, it should be the same principles – you may simply have to look harder for the menu options I mention)
  • Notepad++ (free here)
  • Dreamweaver (or another HTML editor)


  • Windows Notepad (expensive web design software isn’t really necessary)

What We’ll Be Doing:

As with the start of the Smashwords formatting guide, we will start by tagging and then removing any and all formatting. Or at least, so far as Word will allow.

We will then save as a web page, telling Word to keep out the clutter. Word will ignore us and leave in lots of pointless crap we don’t want or need, so we will take the file to Dreamweaver or your equivalent and remove those unnecessary tags.

That’s it.

To see the HTML tags supported by the Kindle, click here. If that looks daunting, we’ll be using very few of them anyway. This is a list of the most commonly used tags. Much smaller.


At this point, you should probably have the book laid out the way you want anyway, but if you haven’t then this is a decent order:

  • Title
  • Copyright
  • Table of Contents
  • Author’s Note
  • The main content
  • About the author
  • Anything extra

Of course, there’s a good chance you won’t want an author’s note, and a table of contents isn’t necessary.

If you’re unsure what kind of copyright page to put in, it can be very simple, or it can go a bit further, like mine:

Copyright © 2012 Ross Harrison
Cover copyright © 2012 Ross Harrison
Cover design by Cui Yuan
The right of Ross Harrison to be identified as the author of this work has been asserted in accordance with the Copyright, Designs and Patents act 1988.
All the characters in this book are fictitious, and any resemblance to actual persons, living or dead, is purely coincidental.
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of the author.

NOTE: If you are doing this after formatting for the Smashwords edition, make sure that the line ‘Smashwords Edition’ isn’t still in your copyright information.


You will want to make sure your em dashes and en dashes are done right. While we’re at it, we might as well make sure your ellipses and quotation marks are right. The latter two won’t look any different on Kindle (actually, the quotation marks may look different on the more modern Kindles), but the dashes will.

If you’ve had the following options selected while writing, and Word has automatically changed your dashes and whatnot, then you can skip this bit.

  1. Click on the big yellow button in the top left of Word, then Word Options at the bottom of the drop down list (in earlier versions of Word, click Tools and then AutoCorrect Options, then ignore step 2)
  2. Click Proofing and then AutoCorrect Options
  3. In both the tabs AutoFormat and AutoFormat as You Type, make sure the options ‘Straight Quotes with Smart Quotes’ and ‘Hyphens with Dash’ are checked


Click OK until you’re back on the manuscript. Now we’ll use Find and Replace:

  1. Press Ctrl+H to bring up the Find and Replace window
  2. Find: “ and Replace: “ (Double quotes will automatically change to the nicer, curved ones)
  3. Find: ‘ and Replace: ‘
  4. Find: – and Replace ^+ (This creates an em dash)
  5. Find: – and Replace ^= (This creates an en dash)
  6. Find: … and Replace: … (In Find, type three full stops (periods). In Replace, press either Ctrl+Alt+. or Alt Gr+. for a proper ellipsis)


In order to make it a little easier when we get to the HTML editing part, we’ll remove all formatting from the document. This means that italic, bold, and underlined text will become normal text.

The problem with this method is that if you had text in italic, bold or underlined, and then deleted it, there may be white space with one of those still applied to it. This won’t matter (except in the case of underline) in the finished product, but I like to keep things as clean and tidy as possible, and so I don’t want that. Because we’re using Find and Replace, you can get around this problem by replacing one instance at a time, ensuring that you skip over anything that isn’t meant to be kept italicised, bold, or underlined. It could get tedious, but you probably shouldn’t have very much of this in the book anyway and I highly recommend doing it this way to ensure no issues.

First, press Ctrl+H to bring up the Find and Replace window. Remember not to type the quotation marks in the following:

– Italics:

  1. Click inside the Find box, then press Ctrl+I and it will say ‘Font: Italic’ beneath the box
  2. Leaving this box empty, now click in the Replace box and type ‘[i]^&[/i]’
  3. Go through one by one, or click ‘Replace All’ (see above)
  4. Click in the Find box again and press Ctrl+I until the format line beneath the box disappears

– Underline:

  1. Click inside the Find box, then press Ctrl+U and it will say ‘Underline’ beneath the box
  2. Leaving this box empty, now click in the Replace box and type ‘[u]^&[/u]’
  3. Make necessary replacements
  4. Click in the Find box again and press Ctrl+U until the format line beneath the box disappears

– Bold:

  1. Click inside the Find box, then press Ctrl+B and it will say ‘Font: Bold’ beneath the box
  2. Leaving this box empty, now click in the Replace box and type ‘[b]^&[/b]’
  3. Make necessary replacements
  4. Click in the Find box again and press Ctrl+B until the format line beneath the box disappears

If for some reason you want to enclose your formatted text between something other than ‘[i]’, etc, you can; the ‘^&’ is the important part. That said, don’t try to be clever and use the HTML tags of ‘<i></i>’, etc, because Word will assume later on that you want it to literally look like that, and replace those brackets with code to display the brackets, rather than making them said tags… Understand? In other words, the result will be ‘&lt;i&gt;Text&lt;/i&gt;’.

Preserving Italics

Do the same for anything else that will need attention, such as chapter headings (except not i, u, or b).


Strictly speaking, this step isn’t entirely necessary, but it will cut down on the clutter when we get to the HTML editing.

  1. Open Notepad++ and create a new file if necessary
  2. In Word, press Ctrl+A to highlight everything, then Ctrl+C to copy it
  3. In Notepad++, press Ctrl+V to paste in your manuscript

It will look confusing and messy, but that’s fine. Don’t try to change anything. Let’s make it slightly less messy:

  1. Press Ctrl+F and click on the Replace tab. Select ‘Extended’ in the ‘Search Mode’ section at the bottom
  2. In the Find box, type ‘\t’ (without the quotes). Leave the Replace box empty, making sure there is no blank space by default, and click Replace All. This deletes tabs
  3. In the Find box, replace the ‘\t’ with ‘\n\r’. Still leaving the Replace box empty, click Replace All again. This will delete blank lines. NOTE: You may need to perform this step again after step 6
  4. In the Find box, replace the ‘\n\r’ with ‘ ‘ (two spaces), and in the Replace box, type ‘ ‘ (one space). Click Replace All. This deletes double spaces
  5. Close the Find and Replace window
  6. Click Edit -> Blank Operations -> Trim Leading and Trailing Spaces. This will delete space before and after paragraphs

You work will still look confusing, but a little less messy. If there are any blank lines, perform step 3 again.

Deleting Blank Lines

Deleting Blank Lines


After saving your Word document, as a new version of course, close it. Now create a new Word document.

In Notepadd++, press Ctrl+A to select everything, and Ctrl+C to copy it. Now go to your new Word document and press Ctrl+V to paste your manuscript in.


Now click the big yellow button in the top left (or File) and then Save As. Save in whatever location you want, under the book’s title, but save as file type ‘web page, filtered’ and add an ‘L’ (but lower case) to the end of the file extension. In other words, it should read ‘Your Title.html’.

Close everything.


Now open your new web page in Dreamweaver (dragging it over the Dreamweaver desktop icon is the simplest way), other editor, or simply Windows Notepad.

If you are familiar with HTML, you’ll probably be relieved at how little code there is. If you are not familiar, you may be worried at how much code there is. The good news is, most of it is the same little bit of code recurring over and over, so it’s easy to get rid of.

To begin with, you’ll find things a lot easier if you understand that almost all HTML tags have an opening and a closing tag. For example, the paragraph tag opens with <p> and closes with </p>. The closing tag always has that forward slash.

First thing to do is find the opening tag ‘<style>’. In Dreamweaver, and possibly other editors (which I will now stop referring to because it’s getting annoying), the tag is in pink font, but obviously in Notepad it won’t be. Highlight the whole style section (remember, that’s from <style> until </style>) and delete it.

HTML Start

That gets the main eyesore out of the way, and you’ll now be able to see the start of your actual content. Let’s start at the top. All that needs to be at the top is:

<title>(Your Book's Title)</title>

So delete anything else and correct the title if need be.

The next thing should be the ‘body’ tag, but it has unnecessary rubbish in it, along the lines of ‘lang=EN-US’. Delete that, and the space before it, so that the tag reads simply <body>.

After the body tag, the next thing you should see is the very first bit of text of your book, preceded by <p>. Delete anything between the body tag and this. In my case, the only remaining thing in between is

. Divs have no place in our particular HTML file.

Next comes a simple but time-consuming process. We need to delete all of the unnecessary code. In the following bits of code, yours may read slightly differently to mine, so make sure to copy and paste from your own file and not this guide. At the moment, what we’re aiming for is to leave every paragraph with only the

tags on either side.

For example, the first paragraph of my first chapter looks like this to begin with:

As his nose cracked under my knuckles, I reflected on how much I hated violence. Not violence stemming from my own unresolved anger issues. That I was fine with. It was violence against women that I hated. I didn’t know why, but the prettier the girl the more I hated it. Maybe I was shallow.

It should read simply:

As his nose cracked under my knuckles, I reflected [...] Maybe I was shallow.

You’ll see that the MsoNormal rubbish is at the start of every paragraph, so it’s easy to get rid of a lot of that clutter:

  1. Highlight ‘ class=MsoNormal‘ (including the space, but NOT the right-hand bracket) and press Ctrl+C
  2. Press Ctrl+F (or Ctrl+H in Notepad) to bring up the Find and Replace box
  3. In Dreamweaver, make sure the ‘Find In:’ box says ‘Current Document’ and the ‘Search:’ box says ‘Source Code’
  4. Click in the Find box and press Ctrl+V (it may already be there in Dreamweaver)
  5. Make sure the Replace box is empty (that includes any blank spaces) and click Replace All

This will take around 30 seconds, perhaps a minute, maybe a little longer in Notepad. Just make sure to save after everything you do, especially with Notepad, as it can be a little temperamental.

You can probably guess what is next.

  1. Highlight ‘‘, this time include both brackets. Depending on where you’re from, this might say something slightly different, such as ‘EN-US’
  2. Open Find and Replace and repeat the above steps
  3. Now do the same with

Now it looks a lot less untidy. It’s mostly your text, with the odd blue (unless you’re in Notepad) HTML tag dotted about.

Go to the very end of the file. After the final

, it should look like this:


Delete that closing ‘div’ tag.

This should conclude the tidy up, because we took it into Notepad++ to get rid of as much formatting as possible. Just in case, though, you should run a search for the following tags and delete them if you find any. Remember to also delete the closing tag. After this, scan it all to see if anything catches your eye. Remember, except for the front matter – which we’ll get to in a minute – you should only see <p> in front of your paragraphs, and </p> at the end.

  • <div
  • ‘<p ‘ (that’s a space after the ‘p’. If you find any paragraph tags with more than just the ‘p’, correct it to simply <p> – there should never be a space)
  • <span
  • &nbsp; (replace these with ‘<br />’ – I’ll mention this again later)


Don’t steal that title, it’s for my Expendables rip off with washed up TV stars. And I’ll sue you.

You’ll be wanting your italics, bolds, and underlines back now, I suppose. If you went through these in the Word document one by one, as I suggested, then you’ll be okay to use ‘Replace All’ this time around. If you did not, then you should probably do so this time. You may find that you have empty paragraphs dedicated to a closing bold tag, or some such. For the sake of tidiness, more than practicality, you might want to fix this. I’ll assume that you did take my advice the first time round though:

  1. Press Ctrl+F (or Ctrl+H in Notepad)
  2. In the Find box, type ‘[i]’ (or whatever you used for italics in Word)
  3. In the Replace box, type ‘<i>
  4. Click Replace All
  5. Now go back to the Find box and type ‘[/i]’
  6. In the Replace box, type ‘</i>
  7. Click Replace All

Restoring Italics

Now do the same process for the underlined and bold tags. Note, though, that there’s no point in putting the title or chapter headings in bold, because we’ll be doing that another way in a minute.

  • Underline: [u] and [/u] should be <u> and </u>
  • Bold: [b] and [/b] should be <b> and </b>


These are the basic tags, and others will rarely be necessary. If you need something that I haven’t covered, refer to the list of tags that Kindle accepts (link)(but not until the end of this guide). If you do, just remember to use the closing tags too (or you could leave a comment asking me).

UPDATE: Since originally writing this, it has become clear that using pixels as a unit of size for font, indents, etc., is not the best way. Kindle users can, of course, make the font whatever size they want, so messing with it isn’t a great idea. Because it is what I have used until now, I will leave it in the below examples, but consider these two points: 1) The basic font size doesn’t need to be set (the very next bit of code I tell you to put between the style tags), and 2) Where it is important to put sizes (such as the text indents), you can use ’em’ rather than ‘px’. Em will change the size relative to what the reader has selected – so a font size of 1.5em is basically 1.5x the font size they have selected. This is handy for things like chapter headings, if you don’t use h2, h3, etc. (coming up).

Paragraph indenting is simple to set up. Go back to the top and, in between the title closing tag and the body opening tag, put in the following:

p {font-size:12pt; text-indent:20px;}

This might be too small an indent for you, but you’ll be able to preview the file later, so unless you already know what you want the indent to be, just leave it like this for now.

The problem with this is that, in fiction, the first paragraph after a break shouldn’t be indented. What we just did says that the indent should occur every time the paragraph tag is used. To get around this, you can go to the first paragraph tag after every break and change that first tag:

<p> becomes <p style="text-indent:0px;">

If, on the other hand, you don’t mind having no indent for paragraphs (perhaps your work is non-fiction), then don’t insert the style bit at the top. Instead, if you find a paragraph that needs indenting, use the above code in the paragraph tag, but put ’20px’, or however much you want it indented.

Now, let’s insert page breaks (i.e. forcing a new page, such as at the end of a chapter). You’ll presumably want these between chapters, and after your title page, copyright page, table of contents page, etc. If you’re familiar with HTML, don’t get a carried away. This simple line of code is exclusive to the Kindle, so you probably don’t know it:

<mbp:pagebreak />

That space before the forward slash is intentional, of course. Always make sure to write your bits of code exactly as written here.

Next, you’ll want some blank lines. If we hadn’t taken the file into Notepad++, it would be riddled with iterations of &nbsp;. Instead of these, we want <br />. That’s a space between the ‘r’ and the forward slash, if it isn’t clear. You may want one of these, or two. In front of my title and copyright information, I’ve used three each to push said bits of content down the page to be more centralised. This doesn’t work with the older E-Ink Kindles, but seems to with the Kindle Fire tablets and Kindle for other devices, and I think it looks better like that. It’s entirely up to you.

The <br /> tag forces a line break. The forward slash tells you that it’s one of the few that doesn’t need a closing tag.

So, for example, the top of my first chapter looks like this:

<br />
<p style="text-indent:0px;">As his nose cracked under my knuckles [...]

Well, actually, it doesn’t, because I have different tags on the chapter heading, but I didn’t want you to get hung up on that before we get to it.

Speaking of which, we might as well do that next. There are different ways of doing this. The most obvious is to use the header tags. That is, <h2> through to <h6>, getting progressively smaller. The <h1> is reserved for the title, so don’t use that. I would go for <h3> personally, but you may prefer <h2>. Anything beyond 3, though, will probably be too small. Again, you’ll be previewing this later, but if it helps at all, the section headings in this guide are <h2>, while the ‘What You Will Need’ and ‘What We’ll Be Doing’, back at the start, are both <h3>. There’s more of a difference on the Kindle though.
The header tags replace the paragraph tags, so the chapter I just showed you would read:


You’ll probably want it centred, so that changes it to:

<h3 style="text-align:center;">ONE | QUITTING TIME</h3>

NOTE: The American spelling of ‘center’ is intentional. Don’t try to change any code to British English, because HTML simply isn’t written that way and it will stop working.

The way I have actually done my chapter headings is like this:

<p style="text-align:center;"><b>ONE | QUITTING TIME</b></p>

Why I did that…I have absolutely no idea. But I’ve done that with everything I’ve published on the Kindle. I have a vague recollection of something to do with a table of contents being automatically generated based on the header tags, but I don’t think that’s a thing. I couldn’t find anything about it when I Googled it. I can’t for the life of me think why I would have done that, but never mind. If you find any issues using the header tags, you can always come back and try it this way instead.

If you have any asterisks or other kinds of symbol for breaks, you’ll probably want them centred. This is as simple as centring anything else we’ve done so far. You’ll also want a space above and below the symbols, so it will look like this:

[...] end of section.</p>
<br />
<p style="text-align:center">* * *</p>
<br />
<p>Start of next section...

I’ll say a quick bit about some other tags you might use:

  • <blockquote> could be used for a newspaper clipping, or a quote from a TV channel, or something like that. It has it’s own margins and indents, setting it apart from the normal text. You can’t use the <p> tags inside it, so use <br /> to create new lines
  • <hr /> creates horizontal line all the way across the page, as seen breaking up the sections of this guide. If my content area didn’t have a fixed width, the lines would span the entirety of your screen. It requires no closing tag
  • <strike> formats the contained text as strikethrough
  • <sub> and <sup> create subscript and superscript


Now we need to format the front matter (i.e. the title page, copyright page, etc.). As I mentioned earlier, the title should be between the <h1> tags. You’ll also want it centred.

<h1 style="text-align:center;">ACTS OF VIOLENCE</h1>

Below this will be your name, also centred:

<p class="author" style="text-align:center; text-indent:0px;"><b>ROSS HARRISON</b></p>

You may have a series title to go above your title; do this the same way we just did the author name, but remove the ‘class=”author”‘ attribute.

Next is the copyright page. This is how I have done mine:

<blockquote style="text-align:center; font-size:10pt;">Copyright © 2014 Ross Harrison
<br />
Cover by Mark Williams, copyright © 2014 Ross Harrison
<br />
The right of Ross Harrison to be identified as the author of this work has been asserted in accordance with the Copyright, Designs and Patents act 1988.
<br />
All the characters in this book are fictitious, and any resemblance to actual persons, living or dead, is purely coincidental.
<br />
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of the author.</blockquote>

The <br /> tags could easily come at the end of the sentences, but I broke it up to make it clearer for this guide. I made the text a little smaller too, for aesthetics’ sake.

If you have an author’s note, or anything else, it will most likely be done just like a normal chapter, except you may want it centred. By now, you’ll be able to work out how to do that.


We’re nearly there now. The table of contents is pretty simple. First, create a page (using <mbp:pagebreak />) and simply copy and paste in your list of chapters. You should include the title page and anything that comes after the main content. Enclose each line in <p> tags.

Next, we need to create anchors and links to those anchors. Go to your first chapter heading and change the line to the following:

<h3 style="text-align:center;"><a name="Chapter 1"></a>ONE | QUITTING TIME</h3>

What you put after ‘name’ is up to you; it could be the actual name of the chapter. This is an anchor, which we can now link to from the table of contents. Do the same for the rest of your chapter headings, title, and any other place you want the TOC to link to. In other words, put <a name="Name"></a> right before text, always inside the paragraph or header tags. Make sure not to use the same name twice.

Next, go back to the table of contents. We’ll now point each one to the right place. So, using the first chapter again, it will look like this:

<p><a href="#Chapter 1">One | Quitting Time</a></p>

The hash tag/pound sign goes in front of whatever you have named the anchor, without a space.

HTML Finished

Now save, go to where you have the file saved and double click it. If it doesn’t open in your browser, then something is probably wrong. It won’t look right in the browser, of course (not least of all because it won’t recognise the page break code), but you can test each TOC link to make sure they go to the right place.


That should be pretty much it for the HTML side of thing. You are able to add images into the work, but that would make the guide even longer, and most people don’t have images. It also raises the delivery cost that Amazon charges. If, however, enough people are in need of help with images, I’ll add it to the guide.

Hopefully I’ve covered enough in this guide that if you need to do anything else, you can piece it together from what’s here. Otherwise, you can ask in the comments. If you require any special characters, simply copying them from Word and pasting them should do the trick; otherwise, here’s a list. Just make sure to preview to ensure it displays on the Kindle properly.

To preview your file, you can download the Kindle Previewer here. All you need to do then is click ‘Open Book’ and find your HTML file. The previewer will then convert the file into .mobi, which Kindle uses, and display it for you as it will on a Kindle. If you go to the top and click on the ‘Devices’ tab, you can switch between various kinds of Kindle to see the difference.

Kindle Previewer

Now that you have the .mobi (it will have saved in a folder in the same location as your HTML file), you can put it onto your own Kindle if you want. The save location will be slightly different depending on what device you are using, but for me, I simply plug my Kindle into the computer, open its folder, open the ‘documents’ folder, and drag the .mobi in. Then you’ll be able to open it on your Kindle for a better idea of how it will look.

Once it is published on Amazon, you’ll be able to download it for free (assuming you sign in to KDP with your main Amazon account), and know for certain that it looks how you want it to. In the very unlikely event that it doesn’t, you can easily update the file even after publication.



This part is pretty simple. Go to Kindle Direct Publishing and sign in with your Amazon account, or create one. On your Author Dashboard, click Add New Title.

The next page will ask you for the book’s details and those of the author. You will also upload the cover and HTML file here. Before you come here, you’ll need to have thought about both Kindle Select and whether or not you want DRM (Digital Rights Management) on your book. I have said a little about the former in the last part of my How to Write a Book Guide, but you’ll need to read about the latter for yourself. I always say no to it.

The second page is where you will price your book and choose your royalty rate. This is either 35% or 70%; each has minimum and maximum pricing requirements. You will also be able to enrol in Matchbook, which means if you have a print copy of your book on Amazon as well, you can give the customer a special price for the ebook if they buy the physical copy.

And…that’s it. Hopefully you found this guide helpful, and hopefully I’ve covered everything most people will need. If you have any questions, let me know in the comments.