Published: July 21, 2025

Time for a Roadmap update!

So far, 2025 has been about polishing the basics and laying the foundation of the next phase of exciting features and improvements. Capacities should just work, and part of this is ensuring all the basics are polished and without friction. We had some work to do here, and have progressed well on it.

We’ve improved the speed, rendering and general editor performance
We’ve improved our offline and export experience, including the long awaited Automatic Export option!
We’ve refined and redesigned several parts of the mobile and tablet experience
We added our Google and Outlook calendar integrations
We’ve added long-awaited object type improvements, such as two-way linked properties and table view customization
We upgraded our AI editor and added 1-click AI autofill properties
We’ve generally squashed lots of bugs and unwanted behaviors, leading to a more consistent and reliable app experience.

In parallel, we’ve been working on migrating to a new database system. This has been very technically demanding for our backend team, but we are now finally done with this. This means we have the foundation we need to take Capacities to the next level.

Now it’s time to look forward to exciting new features and improvements. As always, we have to balance our vision for the app, the valuable feedback we receive from our users, and the technical requirements needed to do this effectively. Here’s what we have planned for the short to medium term.

Object Views & Query Improvements

Objects and queries are the core part of Capacities: all your objects can be displayed in different views and form different perspectives. We’ve already started working on a range of improvements here and we will continue.

We will enhance queries and other content views based on your feedback. The next big items are:

Variable Queries: We’ll add ‘This object’ syntax to queries, so you can reference the parent object in embedded queries
Group by: You’ll be able to group your views by properties which is a necessary prerequisite for Kanban views.
Label property: Instead of having a dropdown that links to a set of objects you will be able to define a set of labels (like status, category, etc.) without using object properties.

There’s more planned here, and we’re excited for you to see!

Readwise Integration

Next up will be the long-awaited Readwise integration!

We have already shared a proposal in our Discord channel and your feedback helped us refine the concept further. The Readwise Integration will be deeply integrated into Capacities, with the goal of genuinely aiding knowledge work, rather than facilitating information overload.

We are now we are working with the Readwise team to work through the technical details and begin phase one of the implementation.

Believers will get access to the Beta version first, the integration will be available for Capacities Pro afterwards.

A better Capacities AI integration

We plan to update several parts of the Capacities AI integration soon. This includes:

A more modern and simpler chat interface: We’ll rework parts of the UI and of the flows around using our chat especially on mobile devices.
Smarter Context: We want to enable chatting with multiple notes, the current week on your calendar, and much more! We will work on the next steps to extend the context the AI assistant gets, so you can do more with it.
Support for other AI providers: Heavily requested and an important addition. We’ll allow you to provide keys for other providers and set your preferences around provider and model choice.

On top of that, we have many ideas on how we want to make the Capacities AI more powerful and smarter. AI will not be a single “feature” but will be integrated into Capacities over time. It, therefore, will constantly be part of our roadmap. More details can be found in the “Longer term” section below.

CSV, Markdown and File Import

The backend changes and our improved databases are essential foundations for building a powerful and reliable import function. We have now started with preparation work and parts of the implementation.

We’re not currently planning to support one-click imports from other apps. Capacities uses a structured, object-based model that fundamentally differs from most tools. One-click imports either assume a similar structure across systems or require complex configuration. Even with that, imported data won’t necessarily map cleanly to our features or set up.

That kind of experience, having to review and fix imported content before even starting to use the app, isn’t something we want to push users into. Instead, we’re focused on designing an import process that provides a better introduction to Capacities and supports more intentional data migration.

Our approach will allow users to import CSV files or folders of Markdown and media files directly into a specific object type. This aligns with Capacities’ model and provides a more transparent and controllable way to bring in bulk content. Nevertheless, we’ll provide guides on migrating from other note-taking solutions. We’ll share more as development progresses.

Search

Our Backend developers have also been collecting feedback on the search functionalities in Capacities. A big thank you to everyone who contributed with detailed reports on our feedback board and in the community.

We plan to full rework our search engine and will incorporate most of the feedback and hopefully all issues with this new design. We also plan to make full-text search available offline.

Longer term

Task Management

It’s our most voted request, and for good reason. We understand the value in being able to derive actions from the insights you find in your notes, and to deal with this in a simple way. We’ve started the conceptual work, and the content view and query improvements are necessary first steps.

We are aiming for a solution that works in the majority of cases. We remain committed in our vision to be the studio for your mind, not a project management app, and that informs our plans. But we promise our solution will be deeply integrated into Capacities, and it’ll just work.

For the more specialized workflows, we will consider developing our existing Task Action features further. Task management will be a Capacities Pro feature.

Media types 2.0

We have been wanting to work on this for a long time now, but given the importance of the above mentioned projects, we had to push it back again.

Working with media is an essential part of knowledge work. We see huge potential to bring working with media in Capacities to the next level. These improvements will be split into several releases that will be released sequentially. Here’s what we have planned:

Overhaul of all existing media types: Standardized views, image zooming, better PDF rendering, audio transcription, a global audio player, and much more!
Media x Search x AI: Each media type has the potential to be made dramatically more useful with the help of search and AI technologies. Next to UI and usability improvements, this will be the main focus point of our overhaul of media within Capacities. Some examples would be searching the content of images or PDFs, automatically generated descriptions for images or transcription for audio files.
Video object type: Video will allow you to save YouTube videos and more as your own object types, enabling you to watch them inside Capacities and take notes.
Email object type: You will be able to send emails to Capacities and save them as email objects. You will be able to take notes, tag them, and search their content.

Deeper AI integration

AI will be a real game changer for your knowledge work, there’s no question, and we see immense potential for AI in Capacities. We are constantly evaluating the latest advancements and technologies and are thinking about how we can best integrate them into Capacities. Here are some fuzzy ideas we have and want to implement over time.

Please note, that we will and cannot add all of them overnight but we see great potential and will work on them.

Related content: Linking helps us to browse our network of thoughts. To help you in that process, we’ll show semantically related content to the current object below your backlink section. You’ll be able to start writing and Capacities will suggest related content. Capacities will become a true assistant that supplies you with relevant content.
Tag page enhancements: We’ll suggest semantically related content at the bottom of your tag pages so it’s not only the content you already tagged but everything that might be related. This will enrich exploration within Capacities.
Advanced AI capabilities: The AI chat will be able to access all your notes as a context when you chat with it. It will also be able to suggest actions like creating new notes, editing existing notes, and more.
Full-text search in media: We’ll add full-text search to PDFs, images, videos, and audio files. This will allow you to search for text in media files and will make discovery within Capacities easier. We’ll also rework extended search to include media search as well.
Understanding media and chatting with media: We’ll add media content like text in images, audio and video transcripts, etc. to the context of the AI assistant. This will allow you to ask questions about the media and to use it in your workflows.

Communication and Feedback at Capacities

We recently crossed 10.000 community members on Discord. We’re grateful for how much thought and care users put into sharing their experiences: it’s a huge part of how Capacities continues to evolve.

As our community has grown, so has the volume of feedback. Over time, we’ve learned that as a small team working across product, infrastructure, support, content, and marketing, we can’t be part of every conversation. To keep delivering, we need to stay pragmatic and focused.

Because of this, we decided to restructure our community engagement as a team. Here’s how our communication channels will work going forward.

Discord will continue to be a space for community discussion. While we will moderate the space, we won’t respond to every message. We’ve reorganized the server to clarify where you can expect communication from the team.

Team communication will happen in these Discord channels:

Announcements – general Capacities updates
Releases – updates about new versions and features
Content Radar – notifications about new content on YouTube or our website

For active discussions with the Capacities team we will actively use:

#feedback-needed – for input on features in progress and broader questions we need some feedback on
#features-forum – to discuss concepts we’re exploring (e.g. Readwise integration, block queries)

After we’ve read through all comments, we’ll share some our thoughts, too. We’ll integrate your ideas into planned features if they align with our vision and strategy (Learn more).

For support we’ll actively monitor:

#urgent – for fundamental issues or problems with your account or the service
#help-and-questions – for questions you cannot find answers to in our documentation, videos, or the app itself.
Feedback board – for bugs, feature requests, and ideas. We’ll redirect you to our feedback board, if they get shared via other channels of communication

All other channels are now considered community-only. They will not monitored for support but we’ll read them for inspiration and engage from time to time if we think it’s needed or valuable.

Together, these changes mean that not all feedback will receive a direct reply, and not every suggestion will be publicly acknowledged, but we’re reading and processing it all. We hope that makes sense to you. Responding to everything is just not feasible for us as a small team and this is the honest answer to that.

A new internal system for processing requests, improvements, and ideas

Internally, we’ve made several changes to help us work more effectively with feedback:

Changes around our Feedback Board: Beth now manages our feedback board, collecting details and following up where needed so the dev team can stay focused. Tickets are typically reviewed Monday to Friday.
Internal organization of feedback: We’ve implemented a new internal system that groups all feedback board tickets by theme. This allows us to run focused development cycles, like our recent work on Mobile and Object View & Query Improvements. While not every piece of feedback will be implemented, each one is now reviewed in context, giving us a more unified and intentional approach to development.
Asking for specific feedback on Discord: When planning larger features, we host dedicated feedback sessions in Discord in the above-mentioned places to gather structured input.
Linking it back: Where relevant, release notes will link back to the feedback tickets that inspired new features or fixes.
Reflection on releases internally: After major launches, we’ll begin sharing post-release insights from the team. We are aiming at launching new releases as flawlessly as possible without introducing any new bugs.

We hope this provides clarity on the changes we’re making. These updates reflect our current approach, but we may continue to adjust our systems as needed. We’ll keep you informed of any future changes.

Company update

Capacities remains a sustainable business with a growing user base thanks to our paying users. We have also grown a lot as a team in the past months and feel like we’re more productive than ever together. We’re proud of the changes we’ve made in 2025 so far, and even more excited about what’s coming next.

Thanks again for being part of the journey.

What's next?