Google Tests Markdown Note Export in Keep for Android
Google Keep’s trademark has always been simplicity, but power users have long wanted better formatting and flexibility. An APK teardown of Google Keep for Android (version 5.26.191.01.90) reveals a new "Export to Markdown" option hidden behind a debug flag. If fully rolled out, this Google Keep export feature would let users save notes as .md files, a standard format widely used by developers, writers, and knowledge workers. While Keep still lacks native Markdown editing, the ability to perform Markdown note export directly from the app dramatically lowers the friction of moving content elsewhere. Power users currently rely on browser extensions for limited Markdown support on the web, an awkward workaround that undermines Markdown’s promise of simplicity. By contrast, a built-in export workflow on Android would make it far easier to transition notes to more advanced tools without manually copying and reformatting content.
Why Markdown Export Matters for Note-Taking Ecosystems
Markdown is a lightweight markup language that uses characters like #, * and _ to create headings, bold, and italics in plain text. Because it is human-readable and app-agnostic, it has become a de facto standard for modern note-taking and knowledge management tools. A Google Keep export to Markdown would instantly make notes compatible with popular apps such as Obsidian, Notion, Bear, and countless Git-based workflows. Users who outgrow Keep’s simple interface could move their archives without being locked into Google’s ecosystem. This is especially significant for people who want features like bidirectional links, advanced tagging, or local-first storage that Keep does not provide. While the new option is explicitly labeled as a debug feature and may never ship, its presence suggests Google is at least exploring data portability features that respect users’ desire to retain long-term control over their information.
Passkey Portability Comes to Google Password Manager
On the security side, Google is also experimenting with passkey portability inside Google Password Manager on Android. Passkeys promise stronger authentication than traditional passwords, but until now they have been difficult to move between password managers, effectively tying users to a single vendor. Hidden settings uncovered in testing replace the current “Import passwords” and “Export passwords” options with “Import passwords & passkeys” and “Export passwords & passkeys.” In practice, this would allow password manager switching without sacrificing modern authentication credentials. The new flow prompts users to select which password manager currently stores their passkeys, then hands off to that app to transfer stored items into Google Password Manager. While exporting passkeys out of Google to another manager appears to rely on prompts when launching a competing app, the mechanism already works in testing, even if Google has not yet activated it for the general public.
Credential Exchange Protocol and the Limits of Interoperability
The emerging passkey transfer system is built on the Credential Exchange Protocol (CXP), backed by major industry players including Google, Apple, and Samsung. CXP is designed to let different password managers and platforms securely exchange passwords, passkeys, and related data without exposing sensitive information. For users, this means password manager switching can become a guided, secure process instead of a painful manual migration. However, interoperability may initially be limited to providers that adopt CXP, so not every niche or legacy password manager will necessarily participate. Apple’s platforms already support moving passkeys to third-party managers, and Google’s testing suggests Android will follow a similar path. Together, these moves help prevent passkeys from becoming a new form of lock-in. Instead, they push the ecosystem toward a world where secure credentials can move with the user, not just stay bound to one vendor’s walled garden.
A Broader Shift Toward Data Portability and User Choice
Taken together, Google Keep’s experimental Markdown note export and Google Password Manager’s passkey portability testing reflect a broader shift toward user-centric design and data portability features. Users increasingly expect to move notes, credentials, and digital assets between services without starting from scratch. Even though both capabilities are early, hidden, or limited, they indicate Google is preparing for an environment where interoperability is not optional. Native support for exporting notes to .md files helps Keep coexist with richer note-taking platforms, while passkey transfer flows reduce the risk of being trapped inside one password manager. As more platforms adopt shared protocols like CXP and standard formats like Markdown, the balance of power tilts slightly away from vendor lock-in and toward user choice. For many, that could make it easier to adopt Google’s tools in the short term, knowing they can leave without losing their data later.