Bear for Blogging

I had ditched Ulysses when it went subscription but during 2020, I’d paid for the subscription as I’d managed to get a discount code for it. It was good to be able to use it across my devices and it’s still one of the best plain text editors in my view - however, I don’t view it as being worth almost £50 a year - consider that Microsoft charge £60 for Office plus storage space, whereas Ulysses makes use of iCloud space to sync, so I’m not even paying them for syncing!

So I looked around for alternatives, and decided to give Bear a try.


It allows me to drag and drop images in to the application, which I find speeds up my writing process - I then export when the article is finished and deal with the images then (such as sorting the URL’s).

Bear has a number of exports, and can export as a Markdown file, but can include the attachments as well, so it allows for easy editing to post.


However, it doesn’t appear to support tables, at least within its editor. However, you can happily paste a markdown table in to the editor and it’ll be there when you export to markdown, ready for the browser (or in my case, Hugo) to resolve and display nicely!

It just looks a bit odd within notes - especially if not using a monospaced font, like the default Bear font!

And the other item it doesn’t support is footnotes, so I’m not able to auto add a footnote within Bear itself 1.

Though, after some searching, it does appear that these two features will be in the new Markdown editor, Panda, that Bear are implementing and that is currently in Alpha at the minute. In fact, Panda seems to be quite a decent markdown editor by itself!

YAML headers are also proposed for the new editor, which I do use in Obsidian, but not sure I’d make much use of them within Bear - at least not yet, but we’ll see when it’s released.

File Format

Bear uses an SQLite database for its notes, so the underlying notes themselves are not accessible outside the app. Normally, this would be an issue as it’s a closed format (to a degree, as it restricts how I can access and edit the documents I write), but it hasn’t seemed to be an issue yet with Bear, as the editor is good, and it has good export functionality, so I can export the documents as a Markdown file or with Textbundle.


At the minute, I’m running Bear purely on one Mac as a test. However, the annual fee appears to be very reasonable (£13.99 in the UK as I type this) and is far cheaper than Ulysses. Its a fee that I think is fair and reasonable and I think I’ll be paying that shortly to be able to have my notes sync between devices. It would also mean that I can use my favourite editor them - Cobalt!


Something to get used to is that folders don’t really exist within Bear - everything is done within tags. A tag is roughly equal to a folder, but as you can assign multiple tags, the same file can be in a number of tag “folders”. That’s something a bit different but it seems to work. You can also have nested tags, so the file can can be in a “subfolder”. Overall, it works nicely - I just have to make sure that I delete the Bear metadata before posting to my blog.

Incidentally, I’m not sure I think much of the default tag icon assigned to my blog draft “folder”!


For now, I’ll see how I get on with Bear. Writing, it’s nice and simple and works really well. However, time will tell how easy it is to get from writing in Bear to published via Hugo. It’s certainly worth trying for the time being, as the syncing feature, if it works as well as Ulysses, should mean that I’m able to replace Ulysses for writing my blog posts.

  1. Though I can create it using a Keyboard Maestro script using the excellent Markdown library↩︎