A plain-language record of what's changed in NotesXML with each release — what we fixed, what we improved, and what's new.
PDF annotation adds three tools to the toolbar: Underline and Strikethrough for marking up PDF text (select the tool, then drag across the text), and a dedicated Arrow tool in the Shapes menu. All three export as standard PDF annotations visible in Adobe Acrobat and other readers. Also fixed: the Line tool now draws a plain line without an arrowhead — use the new Arrow tool when you want one. On scanned image pages, the text-markup tools are disabled because there is no text to select; the keyboard shortcuts now respect this too.
The Privacy Policy shown inside the app is now identical to the current edition published on the website, adding recent website-side updates that had not yet been carried into the app: the detailed description of what an optionally submitted bug report contains, the explanation that license keys are stored only as one-way hashes, the Dropbox App-folder and permission-scope disclosure, the Report AI Content documentation, and the removal of outdated location-data language. The Terms of Service, EULA, and Refund Policy shown in the app were already current.
The in-app Privacy Policy, Terms of Service, and Refund Policy now reflect that purchases made directly from iwvdigitalsolutions.com are sold through Link, a Stripe service, acting as the merchant of record. Card statements for website purchases show LINK.COM* IWV DIGITAL SOLUTIONS. The 30-day no-questions-asked refund guarantee is unchanged, and Link can additionally issue refunds within 60 days of purchase. Nothing changes for Google Play or Microsoft Store purchases.
PDFs created by the Share function for pages and notes now include the configured left and right page margins instead of running content to the paper edge. Notebook PDF sharing already had correct margins and is unchanged.
The three-dot menus for Notebooks, Pages, and Notes now use one consistent ordering (Set as Home always first, Share always next to Export) and the same Share and Export icons everywhere. Sharing a single page or note as a PDF works again; previously it could silently fail when the Professional Page Numbering print option was enabled.
Notebooks shared from Android as an NXL file are now written in the standard NotesXML file format, so the app can open them like any saved notebook. Previously a shared notebook file could be produced in an internal format the app could not read back.
Sharing a notebook as an NXL or HTML file now names the file after the notebook instead of a generic Notebook.nxl or Notebook.html, matching how PDF sharing already worked. Text and Markdown shares also show the notebook name in the heading and the share subject.
The extra empty band between the drawing toolbar and the page controls is gone on all Android devices, tablets no longer show a gap above the toolbar or a narrowed drawing area, and the bottom of the canvas now stays clear of the system navigation bar. The temporary diagnostics from the previous build have been removed.
This build adds temporary diagnostic logging to pinpoint extra spacing around the relocated drawing controls and a canvas edge issue reported on some devices. No behavior changes; the diagnostics are removed once the cause is fixed.
In the drawing editor on Android phones and tablets, the tool ribbon and the page/zoom bar have moved from the bottom of the screen to the top, just under the title. When drawing on a tablet, the hand you draw with naturally rests on the lower part of the screen — with the buttons there, it was easy to trigger tools, page changes or even Android’s own home/back gestures by accident. The bottom of the drawing area is now entirely canvas. Fullscreen drawing works exactly as before, and nothing changes on Windows or Linux.
On Android, notebooks shared as .nxl files can now be opened by tapping them in Files, Gmail, Drive and other apps — the file-type registration that made this work had been lost in an earlier update. Drawings are also no longer missing from shared output: multi-page drawings now share as one image per page instead of only the first page, every page appears in shared HTML, and shared Text and Markdown list each drawing with its title and page count (previously drawings could vanish from these formats entirely).
On Android, large notebooks reopened automatically at startup were run through a fast-but-flawed loader that could drop drawing content — notes appeared as empty placeholders until you opened the file again yourself. Startup now uses the same reliable loader as opening a file manually, which our measurements also showed is faster. Large notebooks now show a loading screen while they open instead of appearing frozen, and the app’s diagnostic log no longer loses its final entries when you quit.
If your computer has two dedicated graphics cards, large AI models are now split across both cards automatically — including the model’s working memory — so models too big for one card can still run entirely on your graphics hardware, which is much faster than falling back to the processor. When a model fits comfortably on a single card, NotesXML still uses just that card, as before. And when a model fills the available graphics memory without leaving room for its working memory, that working memory can now be kept in regular system RAM instead of forcing part of the model off the graphics cards. Computers with one graphics card are unaffected.
A hidden one-minute limit could cause converting a longer dictation to text to fail partway and start over from scratch, taking much longer than it should. NotesXML now allows the conversion the time it actually needs, based on how long you spoke and how fast your speech model runs on your device. Also, if you quit NotesXML while a dictation is still being converted to text, the recording is now saved to the recovery folder automatically instead of being lost, so you can convert it after restarting.
Previously, if converting a finished dictation to text failed — most often when a large, slow speech model needed more time than NotesXML allowed — the recording itself could be deleted along with the failed attempt. Now NotesXML gives slow models the time they actually need (scaled to how long you spoke and how fast your model runs on your device), and if converting still fails for any reason, the audio is kept safe in a recovery folder and NotesXML offers to convert it again with one tap. On Windows, longer dictations are also no longer cut short at about one minute. A backlog problem that could pile up conversion work behind a slow model mid-dictation has been removed as well, and speed measurements are no longer lost if you quit right after installing a speech model.
NotesXML now measures how quickly your chosen speech-to-text model converts speech on your own computer or phone. If you open Dictation with a model that converts slower than you can speak — which would cause long pauses between sentences and could miss words while it catches up — NotesXML tells you before you start, and offers to switch to a faster installed model with one tap, or to use Continuous Recording instead (which records everything now and converts it to text when you finish). You can always choose to dictate anyway. The measurement happens quietly in the background the first time a speech model is installed or selected, so the advice is ready before your first dictation.
When an action cannot run — for example a page or note was deleted on another device a moment earlier, or no page is open to receive a result — NotesXML now explains it in plain language and tells you what to do next, instead of showing terse internal wording like “Page not found”. A handful of status messages that duplicated an on-screen progress display have been removed, including percentage pop-ups during video conversion and media import (the operation still announces when it starts and when it finishes).
NotesXML now shows far fewer corner notifications. Messages that only repeated what you could already see on screen — a note you just reordered, an event you just deleted, a setting whose control already shows its new value, the app unlocking right in front of you — no longer appear. Cloud sync no longer announces every single file it transfers; you still get the summary when a sync finishes, and every error, warning, and confirmation of things you cannot see (files saved to disk, models installed, exports created) remains. Decorative symbols have also been removed from the remaining messages so they read cleanly with the built-in status icons.
The small notification messages that appear in the corner of the app are now easier to live with. Several messages can stack neatly instead of replacing one another mid-read, any notification can be dismissed with a click or its new close button, and error messages stay on screen longer than quick confirmations so you have time to read them. A message repeated in quick succession shows a repeat counter instead of flashing again, and screen readers now announce errors assertively. Housekeeping in the same release: a few menu entries and messages that promised features 'coming soon' have been removed or wired to the real feature — the Contact List's Import button now opens the working vCard importer instead of a placeholder message.
Android now runs the same speech-to-text engine version as Windows and Linux, bringing the same small accuracy and speed improvement to phone dictation and file transcription. All three platforms are now on one identical, verified engine build.
Android now offers the same speech-to-text model choice as the desktop app: Whisper Base (small and fast to download) and Whisper Small (more accurate, larger download) appear as cards in the setup assistant and in Settings, with install, delete, and set-active controls. Downloads are integrity-verified before use, and your selection persists across app updates. The largest desktop-only model remains exclusive to Windows and Linux. Existing installs keep working unchanged — if you do nothing, Whisper Base continues as before.
Speech-to-text descriptions now match what we measured. Larger Whisper models were described as slower, but on the updated engine the Most Accurate model (Turbo) actually transcribes recordings faster than Small on capable hardware — the real trade-off is memory and disk space, so the model list and an earlier changelog note have been corrected to say so. The setup assistant now also says plainly that the Base speech model is built into the desktop app, so speech-to-text works out of the box with no download; larger, more accurate models remain optional one-time downloads. A build safeguard was added so only intended files ship inside the speech-engine folder.
The Linux build now uses the same speech-to-text engine version as the Windows build, bringing a small accuracy and speed improvement and matching the two platforms. The engine is also now built for broad processor compatibility rather than for the machine that compiled it.
When a long recording was transcribed in sections, a few words could be lost where two sections met. The joining step now keeps everything each section produced and only removes text it can prove is already there, so nothing is dropped at a join. If it cannot be certain, it keeps the text rather than risking losing it.
In the speech-to-text model list, the highlighted card marked the recommended model rather than the one actually selected, so the list could draw your eye to a model you were not using. The highlight now marks the model in use; the star continues to mark the recommendation.
First-run setup said desktop versions bundled the speech model automatically. That was not accurate — the model is downloaded, and the larger models added recently are downloads too. The text now simply states that Whisper models support 99 languages and run fully offline once installed.
Settings, Speech-to-Text now opens the model list directly, where each model shows its size and whether it is installed, and you can install it, use it, or delete it from one screen. The old summary screen has been removed: it described the built-in model even when a different one was in use, and its Uninstall button could remove a model other than the one shown. Deleting a model now names the model and its file first, tells you if it is the one currently in use, and warns you if removing it would leave nothing able to transcribe long recordings on its own.
The Most Accurate speech-to-text model, Whisper Turbo, now transcribes recordings of any length on Windows and Linux. Long audio is processed in short, independently-decoded sections that are then joined back together, which keeps the transcript accurate from the first minute to the last — the earlier short-recordings-only limit is gone, and long files are no longer switched to a different model automatically. Whisper Small remains the recommended everyday choice for its light footprint: Turbo needs about 3 GB of memory and a 1.6 GB download, so choose it when top accuracy is worth the extra space. (Corrected in 5.150.1: on capable hardware Turbo transcribes files faster than Small, so the trade is memory and disk space, not speed.) Everything continues to run entirely on your device.
Clicking outside the Dictate window no longer discards your dictation. If you have said anything, that click is ignored and your text stays put; Cancel, the X, and the Back button now ask you to confirm before discarding. Long dictation also no longer stops silently after five minutes — there is no longer a time limit, and if the microphone stops unexpectedly NotesXML now saves what it captured instead of losing it. As an extra safeguard, dictation in progress is remembered, so if something goes wrong you will be offered the text back the next time you dictate.
On Windows and Linux you can now choose Whisper Turbo, the most accurate speech-to-text model in NotesXML, alongside Base (fastest) and Small (balanced, recommended). Turbo is best for short recordings; for longer recordings NotesXML automatically uses a model better suited to long audio, so you always get a clean transcript. Whisper Small remains the recommended default, and Turbo is an optional download. All models are verified on download and run fully offline. Full-length Turbo support for long recordings is coming in a later update.
In AI Chat's hands-free Conversational Mode, a single spoken turn can now run up to 30 seconds before the app finalizes it, instead of 12. As before, the app normally detects when you stop speaking and responds within a moment of your pause — this longer limit only matters when you speak continuously without a natural break, giving you room to finish a longer thought. Whisper Base remains the transcription engine and everything continues to run on your device.
A second speech-to-text model is now offered on Windows and Linux. Whisper Small (466 MB) transcribes more accurately than the built-in Whisper Base — on a nineteen-minute English test recording it reduced word errors by roughly a quarter — and still transcribes several times faster than real time on a typical desktop. It is recommended automatically on computers with 8 GB of memory or more; Whisper Base remains the default and nothing changes unless you choose to download and activate Small. Both models are verified against a published fingerprint on download and run fully offline. Two larger models are prepared but held back pending further testing on graphics hardware. In Settings, the Speech-to-Text buttons no longer crowd each other on narrow windows.
The 5.145.1 fix shipped the updated model catalog, but the application's internal loader still refused to read it — the file was silently rejected at startup and an older catalog was used instead, so the model list stayed hidden and a warning appeared in the log. The loader now accepts the updated catalog on Windows, Linux, and Android. This also protects Android AI model downloads, which would have stopped working with the updated catalog installed. An automated check has been added so a future catalog update cannot be silently rejected the same way.
In 5.145.0 the new speech-to-text model list did not appear in first-run setup or in Settings on Windows and Linux — both showed only the built-in Whisper Base card. The application shipped with the previous model catalog still selected, and without the updated catalog the model list correctly stays hidden. The updated catalog is now included and selected, and the model list appears as described in the 5.145.0 notes. No transcription behaviour changed in the meantime — Whisper Base continued to work throughout.
On Windows and Linux you can now choose between several Whisper speech-to-text models instead of the single built-in one. Larger models transcribe more accurately — especially in languages other than English — and run more slowly; the model recommended for your computer is starred. Find the list in first-run setup or under Settings, Speech-to-Text, Manage Models. Each download is verified against a published fingerprint before it is used, everything continues to run fully offline, and Whisper Base remains the default — if you change nothing, nothing changes. Android model selection arrives in a following update.
This update lays the foundation for choosing between several Whisper speech-to-text models instead of the single built-in one. The model catalog can now describe a ladder of speech models, each with a size, memory requirement and verified fingerprint, and NotesXML can work out which one to recommend for your hardware. Nothing changes in the app yet: transcription continues to use Whisper Base exactly as before, and no new download options appear. The visible model picker — in first-run setup and in Settings — arrives in a following update, on Windows and Linux first and then Android.
On Windows and Linux, a Table of Contents entry could point at the wrong page. If one section mentioned another by name in its text — for example “see the Sync, Import & Export page for full details” — the contents page took that mention for the section itself and listed the earlier page. Three of the twelve sections in the demo notebook were affected, and one was listed 31 pages early. NotesXML now looks for a heading rather than any mention of the title, so contents entries match the page numbers printed at the foot of each page. The same export also printed its header and footer twice on every page, one copy slightly above the other; only one is drawn now.
On Android, Professional PDF export printed the Table of Contents on the cover page, ran each section straight on from the last instead of starting a new sheet, and left a thin sliver of the previous page — the tail of a line, or a section rule — at the top of the next one. Three symptoms, one cause: this export builds its own PDF page by page, and the page-break instructions in the print layout only take effect when the operating system does the paging. NotesXML now marks those breaks in a form its own export understands. The cover page stands alone, the Table of Contents starts a new sheet, every section begins on a fresh page, and pictures, cards and figures are kept whole rather than split across a boundary — a table that genuinely runs longer than a page still breaks tidily at a row.
On Android, Professional PDF export now prints photographs. Images were being shrunk to about a single pixel by a page-fitting rule that did not apply to this kind of export, so only their captions appeared. Page breaks are also cleaner: a few lines could be drawn twice, once at the foot of a page and again at the top of the next, and a section heading could be left partly behind the footer. Each page now ends exactly where the next one begins, headings are never split, and the contents page points at the page where each heading actually appears. Page margins from your print preset are applied as before.
On Android, Professional PDF export could cut a line of text in half across a page break, and a section heading that landed on a page boundary could be split so the contents page pointed one page early. Page breaks now fall between lines and never inside a heading. The export also uses the page margins from your print preset instead of printing to the edge of the paper — the Professional preset's 1 inch margins are now applied on Android as they already were on Windows and Linux. If a notebook is too long for Professional export on your device, NotesXML now tells you how many pages it supports and offers standard printing, instead of ending without a message.
Android can now produce professionally numbered PDFs: the cover page is unnumbered, Table of Contents pages use roman numerals, body pages are numbered from 1 with correct totals on every page, and Table of Contents entries point at the exact page each section starts on — measured from the final layout rather than estimated. Because Android’s system print dialog does not allow this level of control, professional exports are generated by NotesXML itself and delivered through the Share Sheet, where you can save or send the PDF. Standard printing continues to use the system print dialog unchanged. On devices running an older version of the app, the option remains desktop-only until the app is updated.
On Android, selecting Professional Page Numbering produced PDFs with missing or repeated page numbers and up to 25 percent more pages: the technique NotesXML uses on desktop to renumber pages after the fact is not possible on Android, where the operating system produces the final PDF. Android now always prints with standard page numbering — every page numbered correctly, front matter included — and the Professional Page Numbering option in the print dialog is marked desktop-only until an Android implementation ships. Desktop printing is unchanged.
Selecting Professional Page Numbering without a Table of Contents produced a PDF with no page numbers at all: the professional mode correctly switches off the standard page numbering so the cover and contents pages stay unnumbered, but the pipeline that supplies the professional numbers was only engaged when a Table of Contents was also selected. The professional pipeline now runs whenever Professional Page Numbering is selected, with or without a Table of Contents or cover page. As a safety net, if the professional pipeline is ever unavailable, NotesXML keeps the standard numbering instead of removing numbers entirely.
When you saved a PDF, opened a file, or followed a link, the dialog or browser window could open behind NotesXML or sit as a blinking taskbar icon — most noticeably when using Print to PDF. A dialog takes on the state of the window that owns it, and NotesXML was not bringing its own window forward first, so a dialog opened from a background or minimized window stayed there. NotesXML now restores and focuses its window before presenting any dialog, and gives the hidden page-rendering window used during PDF export a proper owner so it no longer disturbs window ordering. Links and opened files also bring NotesXML forward first, which lets Windows hand the browser to the front.
Four spell-check dictionaries could never finish downloading: the transfer step handled the files as text, which silently altered their bytes, so the security check that verifies each dictionary against its known fingerprint correctly refused to install them — and for German and Polish the text handling also corrupted the dictionary content itself. Downloads are now transferred byte-for-byte, verified against the original fingerprints, and only then converted to text using the encoding each dictionary declares. All ten spell-check languages now download, verify, and install correctly on both desktop and Android.
NotesXML already verifies AI model downloads against cryptographic fingerprints pinned inside the signed app. This release extends that protection everywhere: voice downloads for Read Aloud are now verified unconditionally, every verified download records its fingerprint on your device so “Verify Installed Models” has a permanent baseline, the app cross-checks each model’s exact file size at startup, and downloads that are not listed in the verified catalog are refused rather than installed unchecked. Nothing changes in how you use AI features — this hardening runs silently in the background, keeping everything fully local and private.
After connecting Google Drive — or switching to a different Google account — the next sync could fail with an authentication error even though sign-in had just succeeded, and a second connection attempt was needed. Sync now detects when Google rejects a stored sign-in (for example after access is revoked or the app’s status changes), refreshes or re-requests authorization automatically, and retries — so one sign-in is enough. Disconnecting also now clears the last remaining stored sign-in location.
Choosing Disconnect in Google Drive sync settings appeared to work but quietly left your sign-in tokens stored on the device, so the next launch silently reconnected to the same Google account and the consent screen never reappeared. Disconnect now revokes access with Google and removes the stored tokens from every location the app can keep them, on all platforms. Reconnecting afterward always runs the full Google sign-in, letting you choose the account and review exactly what access NotesXML is requesting.
Connecting Google Drive no longer shows Google’s “unverified app” warning. NotesXML now requests access only to the files and folders it creates for sync — not your whole Drive — which is both a privacy improvement and the reason the warning disappears. Existing sync setups continue to work; your notebooks and sync folder are unchanged.
After buying Professional from Google Play or the Microsoft Store, the app unlocked your features right away — but if you opened the License page before restarting, it still showed the free-tier activation screen asking for a license key. The page now reflects your purchase immediately, showing your edition and plan without a restart. Also fixed: Microsoft Store annual subscribers were shown a “Lifetime license” label on the License page; it now correctly reads Professional (Subscription).
Managing your activated devices and enforcing the 5-device activation limit relies on our license server, and the app’s internal security policy did not include that server’s address — so those checks silently could not run. The address is now approved, and together with new server-side support, device activation, the device list under Manage Devices, and freeing device slots all work end to end. Nothing changes for existing activations.
Requesting your free cross-platform license key always failed with a network error. The app's own internal security policy, which controls which servers the app may contact, did not include our license server — so the request was blocked inside the app before it ever left your device, on both desktop and Android. The license server is now on the approved list, and key requests go through.
Lifetime purchases from the Microsoft Store or Google Play include a free license key for your other devices. Previously that key could only be requested in the moment right after purchase — if you chose Maybe Later or the request failed, there was no way to ask again. The License page now has a Get License Key for Other Devices button whenever a store Lifetime license is active, so you can request or retry the key delivery at any time.
On the Microsoft Store edition, a completed Annual or Lifetime purchase unlocked Professional immediately but the app returned to the Free tier the next time it started, because the startup check that asks Microsoft what you own could not run. That check now works. Your purchase is recorded with Microsoft either way — nothing was lost — and with this version the app recognizes it automatically at every launch. If you purchased on an earlier version, simply update: your Professional tier is restored without buying again.
On the Microsoft Store edition, choosing Annual or Lifetime in the Upgrade dialog always opened our website instead of Microsoft's own purchase window. The component that opens Microsoft's window was unintentionally disabled by a missing optional library, and the app fell back to the website without saying so. That component now runs on its own, and the app records why a fallback happened if one ever does. The website remains available as a backup path, and purchases made there continue to work exactly as before.
A link handler meant to open web addresses in your browser was mistakenly catching in-app links that use the placeholder # address, swallowing the click before the link's own action could run. This is why the startup PIN screen's Use password instead link still did nothing in 5.143.2 even after its own logic was fixed, and it also made the Upgrade to Professional banner link unresponsive. Those links now work; real web, email, and file links still open externally as before.
Two startup security fixes. First, turning off Lock on Startup (Settings > Security Settings) previously had no effect — you were asked for your PIN or password at every startup regardless. The setting is now honored: when it is off, the app opens directly. Second, on the startup PIN screen, the Use password instead link did nothing (it could even leave you on a blank locked screen); it now correctly switches to password entry, and Cancel on the password screen safely returns you to the unlock prompt instead of leaving the app stuck. Also fixed: after unlocking with your password at startup, opening a password-protected document later in the same session now correctly checks the document's own password.
The PIN field under Settings > Security Settings > PIN Protection only let you type 4 digits, even though the setup wizard and the unlock screen support 4-6 digit PINs. The field now accepts 4 to 6 digits, matching the rest of the app.
Pressing Sync Now as a Free user could do nothing at all: the sync panel button was disabled (a dead tap, especially on Android), and the Dropbox settings Sync Now could be silently skipped. Both now show the Professional upgrade message so you always get a response. If you have already seen the message once this session, automatic syncs will not repeat it.
On the Free tier with cloud sync configured, the Professional Feature upgrade message could appear again right after you dismissed it, because two automatic sync attempts each showed their own copy. The message now appears at most once per session. Choosing Not Now really means not now.
If you set a 5- or 6-digit startup PIN, the unlock screen previously showed only four boxes and could never accept the full PIN, locking you out of the app. The unlock screen now shows the correct number of boxes for your PIN, plus an Unlock button, so 4-, 5-, and 6-digit PINs all work. If you were affected, simply enter your real PIN on this version to get back in — no data is lost.
On the Free tier, the Professional Feature upgrade prompt (for example, the one shown when turning on Cloud Sync) could occasionally appear with its Upgrade, Not Now, and tap-outside actions all unresponsive, and the Esc key did nothing. This happened when the prompt was shown more than once in a single session. The prompt now clears any earlier copy before appearing, every button responds reliably, and pressing Esc (or the Back button on Android) closes it.
If a Professional-tier AI model was selected while licensed, it previously stayed selected and working after the license was deactivated or expired. Now, when a license ends, the app automatically switches to the best free model (your downloaded model files stay on disk, and re-activating a license restores access instantly). The AI engine also independently verifies the selected model's tier before every session.
On Free-tier installations (including after a trial ends), AI Chat could still be opened from the AI toolbar button — the license check covered one way of opening the chat but not the toolbar route. All ways of opening AI Chat now show the upgrade prompt on the Free tier. Professional licenses are unaffected.
After the Beta label was retired in 5.142.91, eight of the app's built-in self-test checks still expected version numbers to start with 'Beta' and reported failures on a healthy installation. Those checks now accept the current version format (and still recognize older Beta-labeled builds). No app functionality was affected — only the test suite itself.
The 'Purchase a license' link on the license activation screen pointed to a web page that does not exist, showing a 'page not found' error. It now opens the current pricing page. Every website link in the app was also checked against the live site as part of this fix, and an automated check now prevents broken links from shipping in future releases.
On the Microsoft Store edition, the Annual and Lifetime buttons in the Upgrade dialog now open Microsoft's own purchase window — pay with your Microsoft account, no license key needed, and your purchase follows your Microsoft account. A new 'More purchase options' link offers direct website purchase (including academic pricing) as an alternative. Also, NotesXML has graduated: the version label no longer carries the Beta prefix.
Clicking Annual or Lifetime in the Upgrade dialog on the Microsoft Store edition opened the website at an old address that no longer exists, showing a 'page not found' error instead of purchase options. The buttons now open the current pricing page. The academic verification service was pointed at an outdated address with the same problem and has also been corrected.
Misspelled words were underlined in red, but right-clicking them offered no way to fix them — the context menu showed only editing commands. Right-clicking a misspelled word now lists up to five suggested corrections (click one to replace the word) plus an 'Add to Dictionary' option, followed by the usual editing commands. On Android, the system's own text-selection toolbar already provides spelling suggestions and is unchanged.
On Linux systems where audio plays through a TV or monitor (HDMI or DisplayPort), the first word of spoken responses could be partially cut off — these audio outputs take up to a second to wake after sitting idle, longer than the built-in silence padding. NotesXML now keeps the audio output awake during speech sessions, so every response starts cleanly. This is the desktop counterpart of the Android fix in 5.142.84.
When an AI response contained only numbers or a plain equation (like a list of digits or '2 + 2 = 4'), the text-to-speech skipped it entirely — a filter meant to suppress stray list markers was discarding all content without letters. Numbers and equations are now spoken, and simple math reads naturally ('2 plus 2 equals 4', '15 percent'). Stray list markers between sentences remain correctly silent.
When the AI spoke a response or read a note aloud on Android, the first word was clipped or lost entirely — the device's audio output takes a moment to open, and the beginning of the speech was swallowed while that happened. NotesXML now holds the audio output open during speech sessions, so every response and every reading starts cleanly from the first word.
When importing a large file (such as a big CSV), the 'Opening File Dialog' helper message could remain on screen through the entire import — long after you had already chosen the file — and disappear only when the import finished. The message was actually being dismissed on time, but the import work started so quickly afterward that the screen never got a chance to redraw. The app now guarantees one screen update between closing the dialog and starting the import, so the message disappears the moment you pick a file and only the import progress indicator remains.
The previous fix connected the video player to Android's secure storage, but the app's built-in content security rules — which had no rule for media — were still blocking the video before it could load. A media rule now explicitly allows the app's own stored videos. Desktop playback is unaffected. The video format itself was verified fine all along.
Videos saved to your notebook's Media/Video folder on Android imported correctly but showed 'Video could not be played' when opened. Android's storage security blocks the direct file path the player was given, even though the app saved the file through the proper channel. The player now opens videos through the same secure storage permission used to save them, so externally stored videos play normally.
A cluster of controls were wired to functions that never existed, so they failed without any message: the Ctrl+Shift+S Save As and Ctrl+O Open shortcuts in the mobile drawer, CSV and HTML imports from the drawer (the file was read and then discarded), all file imports launched from the search palette (Evernote, Markdown, HTML, text, XML), and the calendar Contact List, which always showed 'No contacts yet' even after you created contacts and threw errors when you typed in its search box. All of these now call the real functions: the shortcuts save and open, the imports import, and the Contact List shows, searches, sorts, and filters your contacts. JSON import, which was never actually supported, now says so instead of doing nothing.
Importing a video and choosing 'Save Externally' (or importing any video over 100 MB, which requires external storage) always failed on Android with 'External storage not available on this platform'. Android can now save videos to your notebook's Media/Video folder just like desktop. Videos are transferred in small pieces, so even very large files import without exhausting memory.
When printing with Professional Page Numbering and Section Headers turned off, the printed table of contents showed no page numbers at all (body pages numbered correctly). The hidden markers the print system uses to locate each section were being dropped from the PDF's text layer by the rendering engine, so the table of contents could not find where sections started. The markers now survive, and every table of contents entry shows its correct page number.
If your antivirus quarantined part of the AI engine (this has happened with Avast), NotesXML used to retry pointlessly and then show a generic startup error. It now detects the missing file immediately and tells you exactly what happened and how to fix it: restore the file from your antivirus quarantine and add an exclusion for the NotesXML folder, or reinstall NotesXML.
On Windows and Linux, calendar reminders can now also appear as system notifications (in addition to the in-app alert window added in the previous update). Clicking the notification brings NotesXML to the front. You can turn this on or off under Settings > General > "System notifications for reminders" — it is on by default. Note that your operating system's own notification settings (such as Windows Focus Assist) still apply.
In timezones behind UTC (all of the Americas), calendar items could display — and in some views, be filed — one day early: an event note dated July 16 showed "July 15," tasks near a month boundary could appear under the wrong month, overdue calculations could be a day off, and a today event could vanish from Upcoming Events. All fixed. Also: reminders for timed events and tasks used to appear only as a brief 10-second popup message, easy to miss — every reminder now opens a proper alert window that stays until you dismiss it, and a reminder time you set yourself is now honored for timed items too.
If a task reminder and an event reminder fired at the same minute, the second one silently replaced the first — you could miss a meeting alert without ever seeing it. Both reminders now appear together and are dismissed separately. Also fixed: the password strength meter in Settings > Security never responded while you typed (it was accidentally wired to a different, hidden meter); it now works, and resets properly when you cancel.
Two components were silently missing from Windows packages: the built-in English spell-check dictionary (spell check needed an internet connection the first time you used it) and a small helper that instantly frees your graphics card's memory if NotesXML is force-closed or crashes during AI use (without it, the memory was only reclaimed the next time you started NotesXML). Both are now built, verified, and included in every Windows release.
When AI features were switched off, searching the command palette for "Settings: AI" found nothing — the one entry that leads to the switch for turning AI back on was hidden along with the AI features themselves. The palette now always lists Settings: AI (except in editions built without AI), so both routes to re-enabling AI — the settings menu and the palette — stay open.
If you switched off "Enable AI Features," the AI Model settings page refused to open afterward — which meant the switch to turn AI back on was unreachable, even after restarting. The settings page now always opens (the switch lives there), so disabling AI is a choice you can reverse at any time. Also removed a duplicate, non-working "Enable Punctuation Enhancement" toggle from the model manager that could silently affect the main AI switch; punctuation enhancement follows the main AI Features switch.
Since late June, the AI engine could silently run on your computer's processor even when a capable graphics card was available, making AI responses much slower than they should be — on Windows and Linux alike. The way NotesXML asked the AI engine which graphics cards exist had stopped working after an engine update. Hardware detection now asks directly and reliably, works with any number of graphics cards, and re-tests automatically. If AI felt slow recently, this update should restore full speed; the first launch will re-check your hardware once.
Added deeper hardware-detection notes to the on-device technical log introduced in 5.142.66 (graphics-driver configuration seen by the AI engine at startup — never your notes or words), so the remaining cases where AI does not use a capable graphics card can be diagnosed from a single report. This build also consolidates the 5.142.66 microphone-detection fix and technical log, which some 5.142.67 build trees were missing.
Entering your license key by pasting it (instead of typing it manually) could scramble the key if its first character after the type prefix happened to be a letter — for example turning PRO-ABCDE-... into the invalid PROA-BCDE-... — causing a valid, purchased key to be rejected as "Invalid key format." The key entry field now recognizes the PRO, ACAD, BETA, VIP, and NXML prefixes directly, so pasted keys are grouped correctly no matter what their first character is. If you previously had trouble activating a key, try again — it will now paste in correctly.
The Microsoft Store edition could fail to find your microphone even after permission was granted, because of how it asked Windows for the device list. It now uses a more reliable method. NotesXML also keeps two small technical notes on your device (about microphone detection and AI hardware selection, never your notes or words) so problems like this can be diagnosed from a single report.
In the Microsoft Store edition, dictation and speaking to AI Chat failed with a microphone permission error, even when your microphone was working everywhere else. The Store package was not asking Windows for microphone access, so Windows refused it and NotesXML could not appear in your microphone privacy settings. It now requests access correctly. Windows will ask your permission the first time you dictate.
On Windows and Linux, NotesXML was accidentally hiding your graphics card from its own AI engine, so AI ran on the processor instead — much more slowly — even on machines with a powerful GPU. Nothing reported an error. This is fixed, and NotesXML will re-check your hardware once on the next launch and start using the GPU if you have one. If your AI has felt slow, this is likely why.
On Android, the components NotesXML uses to talk to Google Play for Professional purchases were updated to Google's newest billing library, as Google requires for all app updates later this year. Purchases, subscriptions, and restoring an existing purchase work exactly as before. If a product can't be offered on your device, NotesXML can now record the specific reason, which helps us fix store problems faster.
Every part of the Report AI Content dialog now follows your chosen theme, including the category dropdown and the additional-detail text box, which previously stayed white on dark themes. Colors come from the same theme system used by the theme picker, so text always stays readable on every theme.
The new Report AI Content dialog now follows your chosen theme like the rest of NotesXML, and its buttons use the same styling as other AI dialogs instead of plain system buttons. The report text itself now also includes the support email address at the top, so if you use Copy Report instead of Send by Email, the copied text tells you where to send it.
Internal build tooling only: the pre-packaging check now understands how the bundled AI engines are packaged today (a small launcher alongside an engine library) instead of expecting older single-file layouts, and now also verifies the speech engine's core library is present. No change to the application itself.
The AI, dictation, and read-aloud engines previously required a Microsoft system component (the Visual C++ Redistributable) that most Windows PCs already have — but on a fresh Windows installation without it, those features would silently fail to start. NotesXML now ships the three required Microsoft runtime files inside the application itself, so the AI engines run on any Windows machine with nothing extra to install. Nothing changes on machines that already worked, and Linux and Android are unaffected.
You can now report AI-generated output that you find harmful, offensive, misleading, or otherwise inappropriate. A Report button appears on every AI Chat response and on every AI action result (Summarize, Translate, Polish, and the rest), and there is a permanent 'Report AI Content' entry under Help & Info. Reporting does not change how NotesXML handles your data: the AI still runs entirely on your device, and nothing is transmitted automatically. Choosing Report builds a plain-text report on your machine, shows you the exact contents, and hands it to your own email app — it is not sent until you send it. The AI's response is included by default, since that is what you are reporting; the prompt or source note that produced it is left out unless you tick the box, because that may contain your private notes.
Completes the previous update: an internal recording detail meant the live dictation text still could not start on Android. Words now appear while you speak, refreshing every few seconds depending on your device.
On Android, the dictation window previously stayed empty while you talked, even though your speech was being captured correctly — the words only appeared in the finished note. The live view now works on Android just as it does on desktop: text appears while you speak and firms up as you pause. On slower phones the live text may update every few seconds; your full dictation is always captured regardless.
Two fixes for extended dictation sessions. First, the live text no longer freezes after roughly a minute of continuous speaking without a pause — the speech engine was re-reading the entire recording for every live update, taking longer and longer until it timed out; it now reads only the most recent stretch, so updates stay fast no matter how long you talk. Second, the view now reliably follows the newest words: previously a single large text update could silently stop the automatic scrolling for the rest of the session. Scrolling up to review still parks the view; returning to the bottom resumes following.
The quick-insert pins next to the + button (which notes you pinned, and the order you pinned them in) are now saved with your other settings and restored exactly on the next launch. Previously they could silently revert to the defaults after closing and re-opening the app. If you had a pin set that kept getting lost, it will start sticking from the first change you make after this update.
During long dictations the live text view now scrolls automatically so the newest words are always visible. Previously, once the view filled up, new text was added out of sight below and dictation appeared to have stopped. If you scroll up to re-read something while dictating, the view stays where you put it and resumes following once you scroll back down.
A small correction to the reorganized Insert menu: Video note loads an existing video file from your device, so it now lives in the Attach group with Image and Gallery rather than under Capture. Capture is now strictly for creating new recordings and photos.
Two refinements. First, the Insert (+) menu groups now follow what each action really does: Audio moved into Capture beside Continuous recording (recording is capturing); Image and Gallery moved into Attach (they insert existing files — the camera captures new ones); Table moved into Notes beside the lists (a table is content you write); and the last group is now called Organization — tasks, events, calendars, contacts, indexes and their management tools. Your pinned shortcuts are unchanged. Second, on Android, dictation and transcription now record through the voice-recognition audio source that speech engines are designed for, which can improve accuracy on many devices; the automatic pause detection may recalibrate itself over your first session or two.
The floating recording bar shown during Continuous recording now displays the same live level meter as the Audio note recorder and Dictation — the color-zoned bar with the peak line — driven by the actual microphone signal. Previously the bar showed an animated decoration that looked like a waveform but was not connected to the sound. If you minimize the bar, the meter pauses to save battery on long recordings and resumes when you expand it. On a small number of configurations without a live signal source the decoration remains.
The Insert (+) menu is now deliberately organized. Dictate moved up into the Notes section, right beside Text — it creates a text note, and now it reads that way. Within every section the most-used items come first and related items sit together: the list types are grouped, image capture options are side by side, tasks and events and contacts each keep their pairs together, and housekeeping actions like Manage calendars sit at the bottom. The Attach section (attachments and links) now appears above Structure. Your pinned shortcuts are untouched.
Dictation now shows the same professional level meter as the Audio note recorder: the color-zoned bar (yellow when too quiet, green when good, red when too loud) with the peak-hold line and level markers. One meter, one meaning, on every surface that listens. Under the hood the meter drawing is now a single shared implementation used by the Audio note recorder on both desktop and Android and by Dictation, so the three can never drift apart again.
Dictation (added in Beta 5.142.44) now works the way you speak: a pause simply finishes the sentence — the text moves into the note preview and listening continues, so you can dictate a whole paragraph hands-free. Press Stop & Insert when you are done to save everything as one text note; Cancel still discards. A live level bar shows the microphone hearing you (blue while you speak). If you stop talking entirely, dictation ends itself after a minute — saving what you said, or closing quietly if there was nothing — so the microphone is never left open. On rare audio setups without live pause detection, the dialog tells you to use Stop & Insert instead.
A new Dictate entry in the insert (+) menu lets you speak instead of type. Your words appear live as you talk, and when you stop (or pause for a couple of seconds) the text is saved as a new text note. Dictation is free on every tier with no time limit — it is an input method, like the keyboard. Only the text is kept; the audio is never stored. Whisper already adds punctuation and capitalization as you speak; for further polish, the free Grammar Polish and Clean Up Formatting actions are one tap away in the note AI menu. Dictation is different from transcription: transcription converts saved audio and video recordings into text and remains a Professional feature (the Free tier transcribes up to 30 seconds). Requires the one-time Whisper speech model download (offered on first use).
When a recording is longer than the Free tier's 30-second transcription limit, the upgrade dialog now offers a third choice: Transcribe first 30 seconds (Free). Choosing it transcribes just the opening of your recording so you can see the transcription quality on your own audio; the result ends with a note showing where it stopped and how to unlock full-length transcription. Works for audio and video notes, the note menu Transcribe action, and the Smart Recorder. On Android the preview is offered for recordings up to 15 minutes long (a memory safeguard); on desktop there is no source-length cap. Professional and trial users are unaffected.
Closed a gap where recording with the Smart Recorder in Record & Transcribe mode, or using its in-recorder Transcribe button, could transcribe recordings longer than 30 seconds on the Free tier. The 30-second Free-tier limit introduced in Beta 5.142.40 now applies on these paths too. Recordings over the limit are always saved as audio notes — nothing is lost — and an upgrade prompt explains the limit. Professional and trial users are unaffected (up to 4 hours). Voice input and dictation remain unlimited on all tiers.
Fixed the Upgrade to Professional dialog (and five related license dialogs: Limit Reached, Trial Expired, Cross-Platform Offer, Subscription Lapsed, and Build Expired) appearing see-through, with the page showing through the dialog and its buttons hard to read. The cause was a malformed style rule that made the dialog background invalid, so the browser dropped it entirely. These dialogs also gained a visible X close button, close when you click outside them, and close with the ESC key (or the Back gesture on Android). The dialogs now correctly follow your light or dark theme.
The Free tier can now transcribe audio and video recordings up to 30 seconds long — enough to try the offline transcription feature before upgrading. Longer recordings show an upgrade prompt and are kept as audio or video notes; nothing is lost. The Record & Transcribe mode can be selected on the Free tier (a notice explains the 30-second limit). Professional and trial users are unchanged (up to 4 hours). Also, transcribing handwriting in drawing notes and running OCR on image galleries now correctly require a Professional license, matching OCR everywhere else in the app.
On the Free tier, AI menu items that require a Professional license now show a small crown badge, and the page-level and notebook-level AI menus show a single clear upgrade line instead of a list of items that would each refuse when tapped. The PDF text extraction dialog also marks its Professional post-processing options (Auto Title Pages, Generate Notebook Title, Executive Summary) instead of showing checkboxes that silently did nothing. Nothing changes for Professional or trial users.
Fixed an issue where several Professional features did not check your license and were available on the Free tier: PDF annotation, some cloud sync entry points, one of the two transcription paths, background audio recording, export without branding, and editing AI prompts. In addition, the Professional AI actions at the page and notebook level (such as Summarize Page, Executive Summary, and Table of Contents), the note-level Translate, Extract Action Items, and Custom Prompt actions, and the OCR, Analyze Diagram, and Scan Receipt vision actions now correctly ask for a Professional license on the Free tier. Nothing changes if you have a Professional license or an active trial — every new install still includes 14 days of full Professional access. Free features (including Describe Image, Auto Title, Polish, and Summarize on a single note) remain free.
After you saved a notebook, a later save (including automatic saves) could incorrectly warn that the notebook was modified outside the app, even though the only change was your own save. The app now correctly recognizes its own saves on every save path. Also, automatic background saves will no longer pop up the "changed on disk" question while you are away — if a real conflict is detected, the automatic save quietly waits and your next manual save will ask you how to resolve it.
On a page with many notes, or a very long note, the scrollbar handle on the right edge of the content area could shrink to a sliver and was nearly invisible on dark themes until you hovered over it. The handle now has a guaranteed minimum size no matter how long the content is, and its color adapts to your theme so it stays visible on light and dark themes alike. The scrollbar is also wider than the old default, making it easier to click and drag. It brightens when you hover or drag it, and it grows and shrinks together with the Interface Scale setting like the rest of the interface. Applies on desktop and Android.
Fixed an issue where the Gemma 4 E4B model could garble dates, numbers, and technical values when answering questions about long documents — for example, quoting a date or figure slightly differently from what the document actually says, or mixing foreign characters into its answers. The cause was an anti-repetition setting (added earlier to stop runaway output during scanned-document OCR) that also discouraged the model from repeating facts exactly as written in the source. The setting is now scoped so runaway-output protection is preserved while facts from long documents are reproduced faithfully. Other models are unaffected.
Fixed a deadlock during AI actions on documents containing hidden content: the 'Security review — Hidden content detected' dialog could appear behind the AI progress window, making its buttons unreachable and leaving the action stuck. The security dialog now always appears on top; choose an option and the action continues normally.
Data safety (important): fixed two serious issues where note content could be lost when saving. Files attached as notes (any file type) saved in one session lost their payload and showed 0 bytes after reopening; and images added as image notes could disappear after reload. Both are fully fixed — new saves are safe. Items affected before this update cannot be recovered from saved notebooks or their backups; please re-attach those files and images from the originals.
AI now reads attached documents everywhere. Page and notebook AI actions (Summarize, Briefing, Key Themes, Conflict Analysis, and more) now include the content of attachments and file notes — Word, Excel, PowerPoint, PDF, and text files — instead of skipping them. Notebook Briefing, Key Themes, and Conflict Analysis use a new hierarchical analysis that processes each page (including its attachments) before producing the final result. Large documents of any size can be summarized: AI Chat offers a “Summarize as Note” option for oversized attachments, and AI actions on file notes process big documents in chunks with progress shown.
New formats: OpenDocument (.odt, .ods, .odp), EPUB e-books, and RTF are now supported by AI features and text extraction. Also fixed: a required ZIP-reading component referenced by the app had never been included in the package — shipping it restores PowerPoint text extraction and Office-document search indexing, and enables the new formats.
New setting: AI Settings → “AI Document Text Limit” controls how much text AI features read from a single document (default 2 MB — ten times the previous limit; adjustable 0.1–10 MB). Documents over the limit are truncated with a clear notice.
Also in this release: the AI Chat speaker button no longer disappears when text-to-speech is briefly unavailable (it now shows an unavailable state and recovers automatically); AI-generated notes from page and notebook actions display formatted text instead of raw markup; text file contents attached to notes are decoded correctly in AI summaries; and saved web pages no longer overflow the AI context window during summarization.
Fixed AI actions (Summarize, Generate Title, Translate, Extract Action Items) on file notes containing Word, Excel, PowerPoint, OpenDocument, or EPUB documents: the AI previously received an internal placeholder instead of the document text and typically replied asking for the document. These actions — and the notebook-level summaries that include such notes — now extract and use the real document content, at any size (large documents are processed in chunks).
Fixed the recommended 'Summarize as Note' option in the dialog that appears when a document attached in AI Chat is too large for the AI context window. Selecting it previously did nothing useful; it now summarizes the full document in chunks (any size), shows progress, and offers to save the summary as a note on your current page.
Fixed the error 'extraction library not available' when attaching OpenDocument files in AI Chat. A required component (the ZIP reading library) was referenced by the app but had never been included in the package — this also silently prevented PowerPoint text extraction and Office-document search indexing. The library now ships with the app, enabling PowerPoint (.pptx), OpenDocument (.odt/.ods/.odp), and EPUB reading everywhere AI features extract document text.
The notebook-level Briefing Document, Key Themes, and Conflict Analysis prompts now analyze the notebook page by page — including attachments — before producing the final result, giving more thorough and better-organized output on large notebooks (per-page findings are included below the final analysis). Conflict Analysis extracts each page's specific claims, dates, and figures first so genuine contradictions are preserved for comparison. The page-level Summarize prompt now summarizes each attachment individually before combining. Also new: files attached in AI Chat now include EPUB books (with chapters read in order) and RTF documents (read as clean text instead of raw formatting codes); EPUB files are also readable by page and notebook AI prompts and file notes.
AI features now extract text from OpenDocument files: Writer (.odt), Calc (.ods), and Impress (.odp). This applies everywhere document text is read — page and notebook AI prompts reviewing attachments, AI actions on file notes, and files attached in AI Chat. Very large documents are trimmed to the same generous per-file limit as Word, Excel, and PowerPoint files. Also fixed: PowerPoint and OpenDocument files can now be chosen in the AI Chat attach dialog (previously PowerPoint files could only be dragged in).
Fixed an issue where an image added to a page (for example by dragging an image file in, or from an AI Chat image) displayed correctly during the session but was empty after saving and reopening the notebook. The image data is now stored correctly. Images affected before this fix cannot be restored from the notebook — please re-add them from the original files.
Fixed a serious issue where a file attached as a note (for example by dragging a document into a page) lost its entire content when the notebook was saved: after reopening, the file showed 0 bytes and could not be opened. The file data is now stored correctly and survives save, close, and reopen. IMPORTANT: files affected before this fix cannot be restored from the notebook — please re-attach them from the original files. PDF notes were never affected.
Fixed an issue where AI summaries involving certain text files contained scrambled, code-like text. Files stored in a particular internal format were being passed to the AI without being decoded first; they are now converted to readable text before any AI processing.
The notebook-level AI summary now follows the full hierarchy: each page's attachments are summarized individually (short ones included as-is, unreadable ones listed by name), each page is then summarized, and a final overall summary is produced. Pages containing only attachments (no notes) are no longer skipped. Also fixed: summarizing a page with a saved web page (.html) attachment could fail with a context error — hidden script and style code is now excluded from the extracted text, and very large content is split safely instead of being rejected.
Fixed an issue where the AI Chat text-to-speech speaker button could be invisible until audio had been produced elsewhere in the app. The button is now always shown: when text-to-speech is not yet available (for example, right after launch while the speech engine is still starting), the speaker appears with a red prohibition mark and an explanatory tooltip instead of being hidden. It recovers automatically within a few seconds once the engine is ready, or immediately when clicked.
AI prompts run at the page or notebook level (Summarize, Custom Prompt, and the other built-in prompts) now include the content of file attachments, not just notes. PDF documents (with a text layer), Word, Excel and PowerPoint files (.docx/.xlsx/.pptx), and text-based files (such as .txt, .md, .csv, .json, source code and logs) are read, with very large files trimmed to a generous per-file limit. Attachments that cannot be read — images, legacy Office formats, audio/video, scanned PDFs — are listed by name in the AI's input as not included, so the response is honest about what it covered. Also fixed: AI actions on text-based file notes previously received the file's raw encoded form instead of its readable text.
Fixed an issue where saving an AI response as a note produced unformatted text (literal ## and ** symbols) even though the response preview showed proper headings, bold text, and lists. Affected: Custom Prompt at the page and notebook level, the built-in page and notebook AI prompts, and Translate Page. The response is now converted to formatted content when the note is created, matching how AI Chat and note-level actions already behaved.
Fixed an issue where downloading the French spell-check dictionary failed. The French dictionary is published in a different location than the other languages, and the app was looking in the wrong place; it now downloads correctly, pinned to a fixed version and verified against a built-in SHA-256 fingerprint like the other languages. All ten downloadable dictionaries (English US/UK, French, Spanish, German, Italian, Portuguese Brazil, Dutch, Russian, Polish) are now integrity-checked. Also fixed: on first use of an AI feature, the one-time AI content disclaimer could appear underneath the processing spinner, leaving the app stuck; the disclaimer now always appears on top and the spinner waits until you continue.
Follows the 5.142.17 groundwork. Spell-check dictionaries that are downloaded on demand are now pinned to a fixed, verified version and checked against a built-in SHA-256 fingerprint before they are installed, for English (US/UK), Spanish, German, Italian, Portuguese (Brazil), Dutch, Russian and Polish. A download that does not match is rejected. (French is temporarily excluded from this check because its dictionary is currently unavailable from the upstream source; that is being addressed separately and no French behavior changes here.)
Internal hardening from a pre-release review, with no change to how you use the app. Text produced by AI features now preserves legitimate right-to-left and left-to-right direction marks (used in Arabic, Hebrew and mixed-direction text) while still removing hidden or invisible characters, and every AI feature now shares a single text-cleanup step. Feature-access checks now fail safely to the Free tier in the rare case the licensing component has not finished loading, instead of momentarily allowing access. Spell-check dictionaries that are downloaded on demand can now be pinned to a fixed version and integrity-checked (SHA-256) before they are installed. A new build-time check prevents a paid-distribution build from ever being packaged with licensing turned off.
Internal test-suite maintenance with no change to the app you use. Two checks in the built-in self-test were corrected: the catalog schema-version check now reads the app's own list of supported schema versions (it had a stale hardcoded copy that started failing after the model catalog moved to schema 2.2), and the checklist-checkbox handler check now actually verifies current behavior (it had been silently passing without testing anything). No app behavior changes.
Two refinements to the AI Models screen. The model tier descriptions (Basic, Standard, Full, Premium, Power) now describe what each tier is best suited for — speed and output quality — instead of implying that lower tiers cannot run certain features. Every model can run every AI feature; the tiers differ in speed and quality. Also, the Verify Installed Models button (Windows and Linux) now sits just below the catalog selector, so its results list no longer appears wedged between the download buttons.
Internal cleanup with no user-facing change: the one-time AI disclaimer is now enforced from a single place in the code (the point where any AI feature starts the model) instead of being repeated across individual features. This follows the 5.142.13 change that made that single place present the disclaimer rather than an error. The disclaimer behaves exactly as before.
Fixed an issue where choosing an AI action before you had acknowledged the one-time AI disclaimer (that AI results can be inaccurate and should be reviewed) could show an error message. NotesXML now presents the disclaimer for you to accept, then continues with your action; if you decline, the action is simply cancelled with no error. This now applies consistently across every AI feature. No change if you already accepted the disclaimer.
The AI Models screen now has a clear way to return to the built-in, verified model list. If you had switched to a custom or imported model catalog, its models show as Unverified and are not integrity-checked; you can now choose "Use verified default catalog" (from the Switch catalog menu, or directly from the Verify Installed Models message) to return to the built-in list, which is part of the signed app and cannot be altered on your device. Switching back re-enables integrity checking. Your custom model list is hidden, not deleted — it stays available under "My Custom Catalog (your edits)" and your selected model is preserved where possible.
When you download a Read Aloud voice, NotesXML now verifies it against a fingerprint (SHA-256) built into the app: the downloaded voice file is matched to a known-good value that ships inside the signed application, so a corrupted or altered download is rejected instead of installed. Voice downloads are also now pinned to a fixed, unchanging version of each file. This is the same protection already applied to AI models. No action is needed on your part; any voices you have already installed are unaffected.
Resolved an issue where Verify Installed Models reported an error for larger models (roughly 2 GB and up) on Windows and Linux, while smaller models and vision packs verified correctly. The check was reading each file into memory all at once, which failed on large files; it now reads them in a streamed fashion, so every installed model verifies regardless of size. Your model files and their fingerprints were never the problem — only the check itself. Re-run Verify Installed Models to see all models pass.
Resolved an issue where AI model verification did not take effect on Windows and Linux: the desktop app was not accepting the updated model list format, so verification stayed off. With this fix the app reads the verified model list correctly, so downloaded models are checked against their built-in fingerprints and the Verify Installed Models button works as intended. If you installed models on the previous version, re-open the AI Models screen; no re-download is required.
Downloaded AI models are now checked against a fingerprint built into the app: each model file is matched to a known-good value that ships inside the signed application, so a corrupted or altered download is rejected instead of installed. The Verify Installed Models button (Windows and Linux) now confirms your already-installed models pass this check, file by file. Model downloads also now come from a fixed, unchanging version of each file. No action is needed on your part; your installed models are unaffected.
Fixed two settings on the newly added Ministral 3 14B model so it matches the other Ministral models: its images are now prepared at the correct 1024-pixel size (was 896), and its repetition setting now uses the standard value instead of being left unset. This resolves two internal self-test warnings. Model quality was already good; this brings the model fully in line with the rest of the Ministral family.
The AI Models screen now offers ten downloadable models instead of eight. New additions: Gemma 4 E2B, a compact vision-capable model suited to phones and smaller PCs, and Ministral 3 14B, a larger vision model for desktops (it needs about 11 GB of RAM, so it is offered on Windows and Linux only). The model list is now ordered from smallest to largest, so you can pick one that fits your device at a glance. Your free-tier models and default selection are unchanged.
Every AI model that NotesXML downloads is now verified before it is used. The app computes a fingerprint (SHA-256) of the downloaded file and compares it against a value built into the signed app; any file that does not match is rejected and removed. Download links are pinned to fixed repository versions, so the models offered by default are locked at release and were tested with this exact version. The in-app 'Check for Model Updates' and 'Load Custom Model' options have been removed — model availability now ships with app updates. Advanced users can still load their own model catalog, but those catalogs now show a one-time notice and mark their models as Unverified, because they are not tested with this version or fingerprint-checked. You can re-check your installed models at any time using the new 'Verify Installed Models' button on the AI Models screen (Windows and Linux).
The AI Models screen now makes clear that downloading a model adds a data pack — no software is installed on your device. (Windows only: the Start-menu and taskbar icons now show the NotesXML logo, correcting a generic placeholder.)
On Microsoft Store builds, the upgrade and trial-ended screens now show both purchase options: an annual subscription at $29.99/yr and the one-time $49.99 lifetime license, matching the pricing on our website. Nothing changed about what you own or pay — this only corrects the price summary shown inside the app.
A build-system correction with no changes to the app itself.
Tables now support selecting whole rows, whole columns, or groups of them. On desktop, hover over a table and click the slim handles at the left of a row or the top of a column (Shift+click extends the selection). On Android, long-press a cell in the table editor and choose Row or Column; long-press another cell to extend. A floating toolbar appears with Copy, Cut, Paste, Insert, Clear contents, Copy as CSV, and Delete (with Undo). Paste replaces the selection and understands data copied from Excel, Sheets, and LibreOffice. Pasting a block of cells into a single cell now offers to split it across cells. Also fixed: pasting multi-line text into a table cell no longer creates a new note by mistake.
When a sync wants to delete more files than your safety limit, NotesXML now shows the count with examples and asks for confirmation instead of silently skipping the batch and reporting a sync error. The new Safe Delete Threshold setting (Sync Preferences → Deletion Safety, default 10) controls when the question appears. Also fixed: deletions recorded while offline now reliably propagate to Google Drive.
Sync's stall detector could not see folder-listing activity, so accounts with hundreds of folders were incorrectly aborted mid-listing with a “Sync stalled” error on every attempt. Listing progress now counts as progress; genuinely hung connections still time out as before.
If a file that was deleted in the cloud is already gone from your computer, sync now records it as complete instead of reporting an error and retrying on every sync. Existing stuck entries clear themselves automatically on the next sync.
Catalog documentation backfilled and internal copies brought back into exact sync — no model, default, or pricing-tier changes. Purely behind the scenes: it keeps the AI model list dependable across app updates.
Insert and delete row/column in table notes now act on the cell you clicked — previously, opening the menu or ribbon made the app forget your selection on desktop, so Delete Column could remove the wrong (last) column. If no cell is selected, the app now says so instead of silently acting on the last row or column. New: Copy Row, Cut Row, Copy Column, and Cut Column on the table ribbon (and the Android table editor) — rows copy as tab-separated text, columns as a list with the header, ready to paste anywhere.
NotesXML now checks at startup that the bundled AI engine (llama-server) is the exact build this version was tested with, and warns you if an installation problem left an older engine in place — the cause of the vision failures diagnosed on 2026-07-06. Build tooling gained matching safeguards so a mismatched engine or model catalog can no longer ship silently.
Running a test script (Settings > Run Test Script) now tells the script its own file location. The Test Orchestrator v2.3 uses this to scan the folder it was launched from automatically — no more clicking through the directory picker to point it at the test folder it is already sitting in. If the folder holds no other test scripts, or on Android, the familiar picker appears as before.
Behind-the-scenes fix: code blocks, indented text, and math formulas in rendered markdown are no longer wrapped inside an invalid paragraph element. Browsers were silently correcting this, so nothing changes visually — the rendered document structure is simply valid now, which also lets automated tests check it reliably.
The third and final route by which a list of dates could turn into a code block: pasting. Copies from terminals, file managers, and code-styled pages carry hidden monospace markup on the clipboard, and pasting that into a note created a code block directly — no importing or AI involved, which is why the two previous fixes didn't catch it. Pasted monospace content now arrives as normal text, one line per line. Deliberate code is unaffected: code blocks copied between your own notes keep their structure, typing ``` still creates one, and the Code button still converts selected text into one. Speaking of which — the Code button previously could not take you back OUT of a code block (it was blocked by the same rule that blocks bold there), so an accidental code block was a trap. Pressing Code inside a code block now converts it back to normal text with each line preserved, ready for Sort Lines and Convert to Table. Notes already saved as code blocks: click into them and press Code once.
Two follow-ups to the previous release. (1) Applying bold (or italic, underline, and the other character styles) to colored text flattened the color back to the theme's text color — the display rule fixed last release protected the colored text itself but not styling applied on top of it. Colored text now keeps its color under any combination of character styles. (2) The previous release stopped markdown FILE imports from treating indented lines as program code — but text arriving through AI Chat, OCR, and Describe Image goes through a second, separate markdown converter that still did it, so an indented list of dates from a scanned screenshot still became a code block. That converter now imports indented lines as normal text too, with each line kept on its own line — ready for Sort Lines and Convert to Table. Code blocks written with ``` fences still import as code everywhere. Notes already saved as code blocks keep their stored form; re-running the extraction produces normal text.
Two fixes. (1) Picking a text color or highlight has been writing the color into the note correctly — but a long-standing display rule, added ages ago to keep pasted text readable after theme changes, was flattening every color back to the theme's text color on screen, in every theme. Deliberate colors and highlights are now shown; the readability protection still applies to everything else. (2) Importing markdown treated any line indented by four spaces as program code — an indented list of dates became a code block, where formatting isn't possible. Indented lines now import as normal text; code blocks written with ``` fences still import as code.
Three related dispatch faults. (1) Bold, italic, underline and the other character buttons could silently apply to the wrong note: when editing a note type that uses the classic editing surface (such as checklists), the buttons were routed to the most recently used rich-text note instead — the note being edited never changed. They now reach the note you are actually in. (2) Inside a code block, character formatting is not possible by design (code blocks hold plain program text — the same rule as in other editors); the buttons used to do nothing silently, and now show a brief notice explaining this. (3) The selection toolbar's “More formatting” menu could lose its connection to the editor after the bottom ribbon hid, making Superscript, Subscript and friends dead — they now always reach the editor.
The line tools counted paragraphs and list items — a code block holding many lines, or a paragraph whose lines were separated with Shift+Enter, counted as a single line. So on exactly the notes these tools are most useful for (pasted logs, date lists, delimited data), the selection-toolbar tiles stayed greyed out and the dialogs reported nothing to sort. Both cases are now recognized: lines inside a code block sort in place, Shift+Enter lines sort with their formatting intact, and Convert to Table reads them all. Works from every entry point and with selections inside the block.
The two text tools only recognized notes stored internally as the newer 'text' type. Text notes in existing notebooks — including notes created from markdown import and most notes in real-world documents — are stored as the equivalent legacy 'richtext' type, and on those the tools quietly declined with a brief notice (or the menu entries were missing entirely). Both stored types are now accepted everywhere the tools appear: the formatting ribbon, the note options menu, the selection toolbar, and the Ctrl+K command palette.
Choosing 'Sort lines…' or 'Convert to table…' from a text note's options menu (the ⋮ popup or the note's edit ribbon) did nothing — the dialog was dismissed the instant it opened by the menu's own closing step, and the menu stayed on screen. The menu now closes before the action runs, so both dialogs open normally. The same tools launched from the formatting ribbon's Sort and ToTable buttons or the Ctrl+K command palette were unaffected.
Internal release: the Long Context benchmark now sizes its test prompts using the model's own tokenizer (previously a fixed estimate could overshoot the context window by ~30% on some models, invalidating results), scales its time budgets to the machine's measured speed in its current thermal state, and reports thermal throttling between the start and end of each model's run. No changes to the app itself.
On systems where Gemma 4 models run on the CPU (Intel integrated-graphics machines, per the 5.141.82 policy), the working context is now capped at 8,192 tokens via the model catalog. Measurements showed CPU prompt ingestion runs around 20 tokens per second on this hardware — an uncapped 32K-token request could take close to half an hour, which feels like a hang. The cap keeps every request bounded and predictable; long documents continue to work through the app's chunked AI pipeline, which operates comfortably within the cap. Systems with a dedicated GPU are unaffected and keep the full context. The internal Long Context benchmark was also made more truthful: runs that fail because tasks exceed the time budget now report 'Timeout-Bound' instead of the misleading 'Severe Context Loss', tiers that cannot complete are skipped instead of grinding for hours, and capped tiers are labeled as capped.
Beta 5.141.82 shipped with a coding fault that quietly disabled the AI memory/offload planner on every model start: all models fell back to a legacy full-GPU path, which meant the new Gemma-4-to-CPU routing on Intel integrated graphics never engaged, and Gemma 4 models could still monopolize the GPU — including failing long-context work outright on that path. Fixed: the planner runs again for every model, Gemma 4 models genuinely route to the CPU on Intel iGPU systems (where long-context features also work correctly, since the GPU-specific safety restrictions do not apply on the CPU path), and all other models keep their normal GPU plans. Discrete NVIDIA/AMD/Arc systems remain unaffected.
On laptops and desktops whose only GPU is Intel integrated graphics (Meteor Lake / Arc iGPU class, Windows and Linux), Gemma 4 models no longer offload to the GPU. Benchmarks showed GPU offload of this family on these chips is slower than the CPU (Gemma 4 12B managed 2.1 tokens/s while pinning the GPU near 86% and 90+°C; the same class of model on CPU reached 2.9 tokens/s) and could destabilize under sustained load. A metadata quirk in one 12B model file had let it slip past the existing safeguard — the routing is now independent of model-file metadata, driven by the model catalog with a built-in family fallback. Systems with a dedicated NVIDIA, AMD, or Intel Arc discrete GPU are unaffected, as are all other model families.
The editing improvements from this series are now fully discoverable: 'Convert Table to Text/CSV' joins Sort Lines and Convert to Table in the Ctrl+K command palette; the Help guide gains a Text Tools & Drag-and-Drop section; and the demo notebook's Text Notes & Formatting page adds three try-it notes — a sortable meeting list, a CSV-to-table exercise, and a guide to the single left drag handle. Documentation set (GUI spec amendment, editing scope boundary, SRS and Cross-Reference updates) ships alongside this release.
During a drag, the semi-transparent ghost of the item could be pulled into the page layout by the item's own styling rules instead of floating above it — compressing all three panes and leaving a black band across the lower part of the window until the drop. The ghost's geometry is now pinned so it always floats over the interface. Purely cosmetic: drops, dialogs, and reordering were unaffected.
Internal drag and drop — reordering notes and pages, moving notes to other pages, moving pages and notebooks to other notebooks — no longer uses the browser's native drag system, whose Linux cursor pipeline kept showing a red 'no drop' circle no matter what the app told it. Drags are now driven directly by pointer events: press the drag handle, move a few pixels, and a ghost of the item follows the cursor with a steady grabbing cursor the whole way. The outcome pill, target highlights, and insertion indicators work as before, and dropping calls the exact same actions — reorder, or the move/copy dialog. Invalid spots simply show no highlight and no pill; there is no forbidden cursor anywhere, on any platform. Escape cancels a drag in progress. Dragging files in from your computer, and Android long-press reordering, are unchanged.
Notes previously showed two different drag affordances: the three-line handle on the left of the header and a six-dot handle on the right — one from each of the app's two drag systems. The left handle is now the single drag surface for notes, matching the page drag handle in position and symbol, and it drives everything the right handle used to: reordering with the slot indicator, moving notes to other pages, and Android long-press reordering (now on the left handle, with a full-size touch target). Pages also tighten up: with a mouse, page drags now start from the page's drag handle rather than anywhere on the row — on Android, long-press anywhere on the page row still works.
The 5.141.76 arbiter was being silenced before it could speak: the pane-wide drop zones stop drag events from ever reaching it, so the blocked cursor persisted across the panes. The arbiter now intercepts drags ahead of every other handler, which no handler can block. The move cursor and the outcome pill now hold across the entire journey, and the blocked cursor is set explicitly — not left to chance — over the few genuinely invalid spots. Verified in an automated browser run against the real build. Drop behavior remains untouched.
Dragging a note or page used to show the red 'no drop' cursor across much of the journey even though the drop would work — two internal drag systems each answered only for their own targets. A single drag session now arbitrates every internal drag: the move cursor stays on for the entire valid path, a small pill next to the cursor names the outcome before you commit ('Move / copy — choose on drop' over another page or notebook, 'Move here' for reordering), valid targets highlight consistently, and the blocked cursor now appears only where a drop is genuinely impossible — such as a note over its own page entry. Drop behavior itself is unchanged: reordering, the move/copy dialog, and dragging files in from your computer all work exactly as before.
Text notes gain two long-requested tools. Sort lines orders the lines of a note or a selection — A to Z, Z to A, numeric, natural (2 before 10), reverse, or date-aware, which understands lines beginning with dates like 2026-07-04 09:30 and sorts them chronologically — with options for case-insensitive sorting and removing duplicate or empty lines; while editing, the whole sort is one single Undo step. Convert to table turns selected lines (or a whole note) into a proper table note: the delimiter is detected automatically (commas, tabs, semicolons, pipes, multiple spaces — or date-shaped lines like 2026-07-04 09:30 Meeting notes, which split into date, time, and subject columns), with a live preview, a first-row-is-header toggle, and the choice to insert the table after the note or replace the original (undoable from the toast). Tables gain the reverse: Convert to text/CSV. Find everything on the format row, the selection toolbar’s … menu, the note’s ⋮ menu, and the command palette.
When you select text, the small floating toolbar (bottom bar on Android) has been completed and unified with the main formatting row. It now carries Strikethrough and a Text color picker alongside Bold, Italic, Underline, Highlight, Link, and Checklist, uses the same icons as the formatting row so the two read as one system, and gains a trailing … button opening a small menu with the rarer selection options: superscript, subscript, inline code, a custom highlight color, and clear formatting. Everything works in regular text notes and inside table cells alike, and your selection is preserved through every action — including a round trip through the … menu.
Publishing preparation: every program file inside the Windows package is digitally signed through a cloud signing service, and the build previously requested a fresh security token for every single file — dozens of rapid requests, where one momentary network or service hiccup aborted the whole build after most files had already signed successfully. The build now requests one token per build and reuses it, retries briefly if the service stumbles, and refreshes automatically if a token stops being accepted mid-run. A new self-check also lets the signing credentials be verified at any time without running a build.
Follow-up hardening from the same build-system audit. When the packaging check finds the bundled AI engine isn’t the version it should be — which can happen when the build folder is synced between machines and an older copy briefly reappears — the build now replaces it with the correct engine automatically instead of stopping with instructions. Separately, the step that embeds sign-in credentials could fail to start yet the build continued anyway; any failure there now stops the build outright, at every security level, so a package can never ship with sign-in disabled.
Two build-system checks reported false alarms on every single build: an “incomplete application” warning triggered by an ordinary word in an internal change log, and a credentials check that flagged a harmless internal marker belonging to the text editor’s markdown engine. Both checks now look for exactly what they are meant to find — and the incomplete-application check, which previously only printed a message and continued, now stops the build outright if it ever detects the real thing. Nothing about the shipped application changes; this hardens the process that packages it.
A build-system audit found the Linux package carrying a correctly working but older AI inference engine than its label claimed — the version file had been updated without the engine itself being replaced, and the packaging check trusted the label. The check now asks the engine directly for its version and refuses to package on a mismatch, and the download step verifies each freshly installed engine before certifying it. No user action needed; the affected engine was the same fully functional version shipped in earlier releases.
Two fixes for editing long or structured notes. First, the formatting toolbar attached to the note you are editing used to scroll away with the note — in a note taller than the window you had to scroll back up for every Bold or font change. It now rides at the top of the note and pins to the top of the editor pane as you scroll deeper, staying within reach for the whole edit. Second, clicking into a table cell used to replace the entire formatting toolbar with table controls, making Bold, Italic, fonts, and colors vanish. The character formatting controls now stay put, with the table’s row and column controls appearing alongside them.
Uploading media larger than 2 GB to Google Drive failed with a file-too-large error — files of any size Drive accepts (up to 5 TB) now stream to your account without loading them into memory, for both new uploads and updates to existing files. Production packages also shipped without their product-identity file, silently falling back to a default; the build now stages it correctly and refuses to package without it. Internal version reporting in diagnostics logs is also unified to the real application version.
A delivery check now guarantees that every new version documents itself on this page before it can ship — the newest entry here will always match the version you are running.
This page fell behind again during a rapid run of releases, despite the standing rule that each release documents itself. All thirteen missing releases below are now covered, and the rule is back in force: the newest entry on this page always matches the version you are running.
If you checked “Don’t show on startup,” the Quick Start Guide could become impossible to find again on some platforms. It now has a permanent place in Help & Info (between Help Guide and Load Demo File) and in the Android Help menu. The startup checkbox now means exactly what it says: it only stops the automatic opening at launch.
On phone screens the Quick Start Guide’s sections could collapse into overlapping slivers with their text spilling behind neighboring cards. Each section now renders at its full height and the guide scrolls normally. Desktop was unaffected.
Three fixes from one field session. The “listening” indicator used to appear about half a second before the microphone was actually live, silently losing the start of what you said — the microphone now starts early so it is truly live the moment the indicator appears. Speaking with background noise suppression on your device could make natural mid-sentence pauses count as the end of your turn — the voice detector now rides through those dips. And the per-device voice calibration no longer drifts downward from quiet recordings.
On desktop, the hands-free mode could re-open the microphone while the assistant was still speaking, hear its own voice through the speakers, and reply to it. The microphone now stays closed until every part of the spoken response has actually finished playing. Note: talking over the assistant is not picked up either — the conversation is strictly turn-based.
A build-system correction with no changes to the app itself.
A build-system correction with no changes to the app itself.
The speech engine previously reloaded its voice model for every sentence. It now stays loaded for the whole session, so the first spoken words of a response arrive sooner and short sentences no longer leave small gaps between them.
Conversational Mode on Android previously needed a tap on Done (or a 12-second wait) to finish each turn. Android now detects the end of your sentence from the audio itself, just like desktop. If a turn is finished but nothing was understood, the assistant now says so instead of silently waiting again, and the screen stays responsive while your speech is transcribed.
A recording that contained no actual words (background noise, an accidental press) could gradually teach the voice detector that your speaking voice is as quiet as the room — degrading hands-free turn detection over time. Only recordings with real words now contribute to that per-device learning.
On phones with mixed fast/efficiency processor cores, transcription was spreading its work across all cores and being held back by the slow ones. It now uses only the fast cores — the same fix the AI models received earlier — making each spoken turn noticeably quicker to process.
Two overlapping requests to prepare the AI model could each load a full copy into memory, and on phones the doubled memory use could get the app terminated by the system — sometimes appearing afterwards as a microphone that had gone silent. Only one copy can now ever load; the duplicate request simply waits and reuses it.
AI Chat gains a hands-free mode: tap the conversation button next to the microphone and just talk. The assistant listens, answers aloud, and listens again — no typing or button presses between turns. Say “exit conversation mode” (or start typing) to leave, and adjust the pause length and spoken cues under Voice & Speech settings. A persistent indicator always shows when the microphone is live.
Desktop dictation gained real-time speech/silence detection and rolling interim transcripts under the hood — the foundation for Conversational Mode’s natural turn-taking in the next release. Push-to-talk behavior was unchanged.
The line at the bottom of a saved AI Chat note — which model answered and how fast — previously showed speed figures only for some kinds of responses. Every saved response now reports the same details in the same format, and always names the exact model that produced that specific answer, even if you switched models afterwards.
Creating a note from an earlier AI Chat answer after you had already asked a follow-up question could save the note without your attached image, and could quote the wrong question above the answer. Each answer’s Create Note button now remembers exactly which question — and which attachments — produced it. And when you make a note from a follow-up answer about an image, that image is now included too, marked as coming from earlier in the conversation.
This page had fallen a few releases behind the app. It now covers every release, and from this version forward each release documents itself here — including the one you are running right now.
On shorter windows and phone screens, some dialogs — the PDF transcription and description options among them — could extend past the edges of the screen, leaving the buttons at the bottom unreachable. Every dialog in the app now fits within the screen and scrolls internally whenever its content is taller than the window.
In our production builds, text written by the AI — document summaries in particular — could appear as one long unformatted block, with stray “#” and “*” characters where headings, bold text, and lists should have been. A step in our release build process was interfering with the editor’s formatting engine; that step now leaves it untouched, so release builds format AI output exactly as intended. The app is also several megabytes smaller as a result.
The Errata page introduced in 5.141.46 wasn’t reachable from the Help & Info menu on the current interface — the button had only been added to older menu locations. It now appears everywhere Help does.
The Help menu now includes an Errata page listing what changed in each release, newest first — the same information as this changelog, right inside the app. It replaces the old Version History page, which had fallen far out of date.
The speech-recognition engine now stays ready between dictations instead of starting from scratch every time, so after your first dictation of a session, the next ones begin transcribing noticeably sooner. If the engine is ever unavailable, dictation quietly uses the original method instead — nothing changes in how you work.
While you dictate, NotesXML now receives your recording in finer increments. On systems where audio previously arrived in coarse bursts, in-progress transcription updates could lag behind; they now track your speech in near real time.
When reading AI responses aloud as they arrived, the voice could occasionally say “asterisk” out loud where a bold or italic phrase happened to be split across sentences. Formatting characters are now cleaned up reliably — and as part of the same fix, technical names written with underscores read naturally, tables read as brief pauses instead of “pipe,” and simple arithmetic like 3 * 4 is spoken as “3 times 4.”
Hovering over an item in the AI menu — opened from a note, page, or notebook — could make its text unreadable in several of our light color themes. This also affected the Translate and Convert Code language pickers reached from that menu. Both are now fixed across every theme.
Fixed a rare issue where opening the same notebook a second time — for instance, clicking it twice while distracted — could cause your most recent changes to be silently lost when you saved. NotesXML now recognizes when a notebook is already open and switches you to it instead of opening a duplicate copy. As an extra safeguard, if a notebook ever changes on disk after you've opened it, NotesXML will ask before saving over those changes rather than overwriting them automatically.
When you turn an AI Chat conversation into a note, any images or files you attached are now saved as part of the note alongside the AI's response, instead of being left out.
A “#” character appearing in the middle of AI-generated text — from OCR, image descriptions, or AI Chat — was sometimes mistaken for heading formatting and rendered as a large heading. It now correctly stays part of the sentence.
Settled on the curated set of on-device AI models we're shipping at launch, and corrected an internal image-processing setting that was quietly reducing the accuracy of vision-based AI actions like Describe Image.
On Intel Arc integrated graphics, some AI models — including the Gemma family — don't yet run reliably on the GPU, so NotesXML automatically routes them to the CPU instead. Along the way we fixed a crash that could recur every time you tried again, and a separate issue where "CPU-only" mode wasn't fully disabling GPU use, which was quietly throttling CPU speed. Other models, like our default Ministral 3, already run well on Intel Arc's GPU.
Summarizing an unusually long note or document could overflow the AI's working memory and crash the app. Content is now measured and split more carefully before being sent to the AI, so long documents summarize reliably.
AI actions on Link and Video Link notes now work from a more consistent set of source content and return more focused results.
On Android, a model download could fail without any error message, leaving the model unusable with no explanation. Failed downloads are now detected and reported properly.
Math equations written with our math editor were sometimes missing from printed pages and PDF exports, even though they displayed correctly on screen. They now print and export exactly as shown in the editor.
The Microsoft Store edition of NotesXML now supports purchasing and activating a Professional license directly through the Store, in addition to entering a license key.
In rare cases, other elements on the setup screen could interfere with PIN entry during the security setup step. The PIN field is now fully isolated from anything else on the page.
NotesXML for Android no longer requests photo or video media permissions. Attaching images and files now goes entirely through Android's built-in file picker, so the app can do its job with less access to your device.
This page currently covers every release from 5.141.14 through 5.151.6. Have a question about a specific fix? Contact support.