How to add your own fonts to a Kobo or a Kindle
Kobo's help article, Load fonts onto your Kobo eReader, gives the steps for a Kobo: connect the reader to your computer with its USB cable, tap Connect, and open the drive called KOBOeReader. Put your .ttf or .otf files in a folder named fonts at the top level of that drive (create the folder if it isn't there) and eject. The font then shows in the Text menu, where you tick it under Supplemental before you choose it. A Kindle takes the same steps, except that its fonts folder is already on the drive once the software is version 5.9.6 or later, and it accepts .ttc files as well. Kobo allowed this in 2011; Amazon made it official only in 2018.
Kobo
On 22 June 2011, The eBook Reader reported that a folder called fonts at the root of a Kobo Touch, next to the .kobo and .adobe-digital-editions folders, was all it took. After an eject, the extra faces appeared under Aa beside the seven that came with the device: Georgia, Avenir, Amasis, Delima, Felbridge, Gill Sans and Rockwell. A couple of weeks later Adweek wrote up firmware 1.9.5 for the Touch, which let owners add fonts and change the margins, and which had brought five of those seven built-in faces with it.
Kobo's current help page still sends you to the same folder, though the menus have changed. You open a book, tap the middle of the page, tap the Text icon, tick the new font in the drop-down beside “Supplemental”, and then choose it beside “Font Face”. Kobo lists .otf and .ttf as the supported types, asks you to unzip a downloaded font before copying it, and admits that some fonts don't render properly; its advice in that case is to find another version of the same font. The same page names dyslexia-friendly fonts as one reason to load your own (whether such fonts help readers is a separate question).
A new font won't show up in a PDF: Kobo's page on text settings says you can't change the size or style of the text in a PDF.
Kindle
Before Amazon supported it, owners found a way round. In January 2013 The eBook Reader described a trick for the first Kindle Paperwhite on firmware 5.3.0 or later: an empty file named USE_ALT_FONTS at the root of the drive, a fonts folder beside it, files named Fontname-Regular, Fontname-Italic, Fontname-Bold and Fontname-BoldItalic, and a restart. It needed no jailbreak, but Amazon never documented it, and the site later added a note that it didn't work on the second Paperwhite, released later in 2013.
The supported way arrived with a Kindle software update in June 2018. On 6 June, TeleRead reprinted the readme that the update left inside the new fonts folder. It accepts OpenType and TrueType fonts with the extensions .ttf, .otf and .ttc, and nothing else. You unzip the font if it came compressed, copy the files into the folder, disconnect the Kindle, and choose the font in the Display Settings (Aa) menu. Three days later The eBook Reader listed the models: every Kindle back to the Paperwhite 2, which then meant the sixth to ninth generations, as long as it ran software version 5.9.6 or newer. If your Kindle is one of those and still has no fonts folder, update it first. If you aren't sure which generation you own, the model number tells you. How-To Geek's 2021 guide gives the newer path on the device: Aa, then Font, then Font family.
What the reader does with the files
Copy the whole family, not only the regular file. The 2011 Kobo guide gave the reason plainly: most books use italic and bold, so those files belong in the folder too. Amazon's readme makes the same recommendation, and The eBook Reader's 2018 Kindle guide used a set of four as its example: Georgia-Regular.ttf, Georgia-Italic.ttf, Georgia-Bold.ttf and Georgia-BoldItalic.ttf.
A Kindle also checks what you give it. The readme says a custom font applies “for most books”, and that the Kindle draws the text in its default system font when the font can't be used, for example when it lacks characters the book needs or the file is damaged. The eBook Reader found that a font the Kindle rejects doesn't appear in the font list at all.
The readme ends with a line about rights: you, not Amazon, are responsible for having the right to use the fonts you install. A font under the SIL Open Font License is the easy case, because that licence lets anyone use, copy, embed and redistribute the font, as long as the licence goes with it, and forbids selling the font on its own. A font you bought, or one that came with your computer, has its own licence, and its terms decide whether a copy on an e-reader is allowed.