Homepage    |    GitHub    |    API    |    FAQ

Experimental WYSIWYG editor in Joplin



Wow amazing I will try that right away. Many thanks for your efforts @laurent

That's awesome :star_struck:

That is great news!!

How would this editor affect performance and resource usage? Can it be disabled, once it becomes stable?

It will be optional, even once it’s stable, and if you don’t use it, it won’t affect much.


Super super super great news! Thanks so much!

Do you want feedback on this feature here? I noticed that embedded images are missing. For example:

New WYSIWYG view:


Original split view:

This is the case in many, but not all, notes… both in notes I created and web clippings. I haven’t been able to find any pattern to this just yet!

Will this be available on mobile?

1 Like


1 Like

@Sophia, on which OS? Someone else mentioned they had this issue in Windows but I haven’t tested yet. In macOS it seems to work fine.

Sorry, yes on Windows 10. Otherwise it seems to be working fine, very excited about this new feature :smiley:

Experimenting a little, this is what it shows when I add an image in WYSIWYG:


It actually does NOT show the the image in both the new editor AND split view.

I deleted that and went back to the split view editor and added that same image. Now it shows the image in split view and it's named differently:


But it still won't show in WYSIWYG. Hope that helps with the troubleshooting!

Are there plans to support markdown syntax using the WYSIWYG editor? Is this even possible?

1 Like

This leads to an interesting situation.

On the desktop we can do all kinds of fancy stuff. On the mobile we are limited.
Personally, I do not use the mobile for extensive note taking/editing anyway, but I would like to have access to (view) the information in the notes.
On the desktop I can use a plethora of fancy note taking/editing tools. On the mobile I can use a plethora of simple note viewing tools. Several tools exist that allow me to share desktop and mobile notes. If you’re privacy minded you can use a private cloud like Nextcloud. Otherwise use Drive, Dropbox, etc.

I’m not sure anymore what the added values of Joplin are compared to e.g. NextCloud Notes and QOwnNotes.

No that won’t be supported.

Right, it might have something to do with the %5C that aren’t correctly decoded/encoded. It’s a simple fix so it should work in the next release.

1 Like

Not sure what you mean? If there are alternatives, I guess the question is instead why you’re still using Joplin? And the answer to that will be the added value.

Lots of people prefer to have a few text files they sync on their devices, and that’s fine. Personally I need more than this, and each user will have their own different reasons.

To first answer your question: I’m still using Joplin (for testing, not production) hoping it will get to the point that it will be more useful for me than the alternatives. It has potential.

I think that initially I hoped that Joplin would evolve towards a simple but powerful abstract, cloud backed, notes storage server, accessible via a well-defined API, and complemented by a simple but useful user interface. Other clients could provide dedicated user interfaces using the storage server.

In theory, the storage server is still there (the headless server) but it is merely an API to the SQLite database. Except for the browser clippers there are no tools AFAIK that use the API.

But most important (for me): the user experience of Joplin is still below average. Tools like VNote and QOwnNotes have an advanced user interface, the result of many years of user interface evolution. You can customize the interface for simple and complex use. The Joplin UI is still basic and inflexible. Nevertheless some users will love it since it is what they want. It’s just not what I want.

I am not saying that Joplin is a failure, au contraire, it is an excellent initiative and I hope it blooms. I like a lot of Joplin’s features but after more than a year of trying and experimenting Joplin and I are still not near to the point where I’ll start migrating my vast collection of decades of notes.

1 Like

Thank you, this is a great long expected feature! This is amazing, testing it now.

One thing I’ve noticed is that its Markdown formatting style may be inconsistent with manually written markdown notes by many users. This will break consistency in text formatting once someone changes from manual to WYSIWYG and back, when editing a note.

Specifically, bulleted lists use * and three spaces tabulation (while many might use - and a single space), with an empty line in-between the items.

Is that something that can be left configurable, so that users can adapt to their own style?

1 Like

No, the goal is to generate valid Markdown from the HTML, but there won’t be any attempt to make that Markdown pretty or configurable. For more control over how the Markdown should look, there will still be the Markdown editor.