Desktop pre-release v3.4 is now available (Updated 10/09/2025)

Beta Testing
1

Download the latest pre-releases from here: https://github.com/laurent22/joplin/releases

v3.4.1

v3.4.2

v3.4.3

v3.4.5

v3.4.4

  • New: Add transcribe functionality (#12670 by @pedr)
  • Improved: Make more settings per-profile (application layout, note list style, and note list order) (#12825) (#12714 by @personalizedrefrigerator)
  • Improved: Updated packages jsdom (v26), sharp (v0.34.0), types
  • Fixed: Add tooltips to sidebar buttons (#12798) (#12233 by @suchithms19)
  • Fixed: Date/Time dialog button not visible in dark mode (#12816)

v3.4.6

v3.4.7

v3.4.10

v3.4.12

1 Like
2

v3.4.2

2 Likes
3

I am not sure if this is the right place to bring it up here, but the Jarvis plugin is breaking in the new pre-release v3.4.2. The tools menu option has Jarvis option missing, so does the plugin settings in settings page.
It works fine in the stable build v3.3.13.

1 Like
4

v3.4.3

1 Like
5

Thanks @laurent The v3.4.3 fixes the plugin issue, i will keep testing other things!

6

Hi, I still have plugin issues with 3.4.3 : yesyoukan kanban plugin doesn't work anymore
sorry, my previous kanban eventually appeared normaly, after creating an empty kanban.

1 Like
7

v3.4.5

1 Like
8

I think I just installed this and I’ve noticed a change in the MD window - the Bolded items appear bold, and I only see the double stars when the cursor is on the line of the bolded item. Is this new behaviour because of “improvements” in this version? Or did I inadvertently change some setting in my Desktop app? If it’s new, how can I roll back this change? I really don’t like it at all. The lines jump around when i move the cursor down the page because of the stars appearing and disappearing. It’s horrible. Help me!

Joplin 3.4.5 (prod, win32)

Device: win32, AMD Ryzen 7 5700U with Radeon Graphics
Client ID: ec934152e8ab441e8d1466e69798f9ff
Sync Version: 3
Profile Version: 48
Keychain Supported: Yes
Alternative instance ID: -

Revision: a5d37a0

Backup: 1.4.3
Search & Replace: 2.2.0

Marian

1 Like
9

That's this change:

you can disable it if desired under tools | options | note | render markdown

2 Likes
Markdown Tags Disappear in un-rendered view
Lost a customer today
10

Thank you! I will do that!!!

1 Like
11

v3.4.4

  • New: Add transcribe functionality (#12670 by @pedr)
  • Improved: Make more settings per-profile (application layout, note list style, and note list order) (#12825) (#12714 by @personalizedrefrigerator)
  • Improved: Updated packages jsdom (v26), sharp (v0.34.0), types
  • Fixed: Add tooltips to sidebar buttons (#12798) (#12233 by @suchithms19)
  • Fixed: Date/Time dialog button not visible in dark mode (#12816)
12

Can I just say how much I like this new feature. Means I can almost do away with the view panel.

But also, totally respect that different people have different ways of doing things and the focus that the Dev team haves on making the product flexible is just fantastic. Good on you all. :grinning_face:

4 Likes
13

Yeah I enjoy the feature to render markdown as well (I was using extra markdown editor settings prior to this for that feature!)

I almost never need to use the viewer mode now

1 Like
14

v3.4.6

1 Like
15

Not a fan of this myself when updated to 3.4.6 and very glad this is an option to “revert”. This is one reason why I selected Joplin as an Evernote replacement for my “complicated” notes. I did however find it hard to find the option even with this note, partly I guess platform differences, using this on Mac. (Joplin > Settings > Note > “Markdown editor: Render markup in editor”.

IMHO it is VERY odd how only some markdown is rendered e.g. tables stay in markdown, bold and horizontal lines render - this made me think there was a bug. Feel like maybe this should be an “opt-in” (as in default off) but like any on/off switch some people will prefer it default on, some will prefer default off. Especially in two pane mode it seems like it would be better to have it default off.

3 Likes
16

I can understand it's upsetting when you're fine with the way it currently works, but long term I think that a partially rendered Markdown editor is more user friendly.

  • I agree it should be optional - if you prefer to see all Markdown symbols, that should be possible.

  • I feel that the "render markup" should be on by default because it's more user friendly (no need for a separate viewer, especially for simple notes)

  • But maybe not in this version? It seems it's going to confuse and annoy a lot of people so we should review this carefully first. Maybe there should be a prompt the first time the editor is opened

1 Like
17

As someone who does like the markup rendering, here are my thoughts on how it could be improved/made more user friendly

  1. Don't render the markup in the "split view" (even if the render markup setting is enabled). Split view has a separate preview that's always showing, so users would expect all markup to be displayed in the editor in that mode.
  2. I agree that rendered markup makes a more user friendly default. At some point (maybe after further improvements to the markup rendering) I think it would make sense to change the defaults (for a fresh joplin install) to be editor view only (no preview) with the markup rendered in the editor. A "first launch" prompt for editor mode as laurent suggested could also be a good idea.
  3. It would be nice if the markup rendering was a little more complete, things currently missing:
  • Image embeds formatted as <img>
  • Tables
  • Backslash escapes (these should be hidden on non-selected lines like in Obsidian)
2 Likes
18

I've opened a related issue: Markdown editor: Make it easier to disable in-editor rendering · Issue #13014 · laurent22/joplin · GitHub

1 Like
19
  1. Don't render the markup in the "split view" (even if the render markup setting is enabled). Split view has a separate preview that's always showing, so users would expect all markup to be displayed in the editor in that mode.

I agree with this 100%. I updated this morning and found the partial markdown render in the edit view to be extremely frustrating. When I’m editing the markdown text, I don’t want any rendering. That is what I understand the split view is for. Thank goodness I found the link to disable the render preference otherwise I would have uninstalled and gone back to a previous version.

When I edit in the rendered view I find there are always spaces added to the start of numbered lists and there are added lines added between sections. These additional spaces in numbered lists and additional lines makes the raw markdown list look off and extends notes down the screen and requires more scrolling.

Please leave the edit window as clean markdown without rendering.

If someone wants to edit in the rendered text, then by all means. I can see this to be more user friendly to new users but then please make sure it creates clean markdown and not add spaces or additional lines.

3 Likes
20

Summing up here how to revert the recent markdown editor major change depending on your OS:

Windows => tools | options | note | render markdown

MacOS => Settings > Note > “Markdown editor: Render markup in editor”.

Tbh I would never have found it by myself if I did not read that thread. I would have looked for it in Settings > Markdown. Imho all markdown related options should be there for a more intuitive settings experience. My 2cts.

Such a major change should maybe have been opt in instead of opt out. I guess it was a tough call. Kudos for innovating and keeping the app flexible at the same time.

1 Like