Current optimizations & roadmap
Last updated: April 2026 (v1.0.16)
Verso is built by one person. I read every bug report and every feature request. Critical issues (data loss, crashes) get priority. Everything else gets addressed in the next release when possible. I would rather be honest about timelines than make promises I cannot keep.
Currently optimizing
Things I am actively improving.
Table borders can lose exact widths after editing
When you edit a DOCX with complex tables, some border widths and cell backgrounds may shift slightly on save. Verso preserves the original values when it can, but AppKit's text system sometimes overrides them.
HTML import is best-effort
HTML files are rendered using macOS native conversion. Simple pages look great. Complex layouts, custom CSS, and JavaScript-heavy pages will not render perfectly.
RTL text support is limited
Right-to-left languages (Arabic, Hebrew) are not yet fully supported. Paragraph direction and mixed-direction editing need further work.
Considering
Things I am thinking about. No promises, no timelines.
Bookmark and cross-reference support within documents
Additional spell-check language packs
Template system for common document types
Style check and grammar suggestions
Font embedding in exported PDFs
Not planned
Things I have decided against, to keep Verso focused.
Cloud sync or accounts. Your files are yours. I will never require an account or store your documents on a server.
Real-time collaboration. Verso is for focused, single-author writing. Collaboration tools add complexity that conflicts with the core experience.
Plugin or macro system. Extensibility adds surface area for bugs and support burden. I would rather ship a smaller app that works reliably.
Found something not listed here?
Email hello@versowriter.app with your macOS version, the file you were working with, and a screenshot if possible. That’s all I need to investigate.