Free browser tool · zero cloud lock-in

Google Keep Export Inspector

Inspect Google Takeout Keep archives, audit schemas, detect unexpected fields, and inventory checklists and media.

Runs 100% locally in your browser. Audit your Google Keep Takeout archives before migrating to Markdown or Obsidian. Detect undocumented schema fields, inventory checklists, verify audio and drawing attachments, and export formula-safe CSV ledgers.

Step 1: Paste Google Keep Takeout JSON or HTML

Paste the contents of a Keep JSON note file, an array of JSON notes, or legacy Takeout HTML markup.

Load Sample Fixtures:

Step 2: Archive Inspection Summary

Audited note classifications, checklist completion metrics, and media risk flags.

3Total Notes2 active · 0 archived
1Checklist Notes2/4 tasks completed
2Media Attachments0 imgs · 1 audio · 1 sketches
2Unexpected FieldsunknownClientMetadata, experimentalReminderUsec
Schema Drift & Archive Warnings:
  • Detected 2 unexpected field(s) ("unknownClientMetadata", "experimentalReminderUsec"). Google Takeout schema may have updated or includes undocumented properties.
  • Archive contains 1 trashed note(s). In Google Keep, Takeout includes the Trash bin by default.
  • Archive contains 1 audio attachment(s). Many Keep voice notes use .3gp or .amr formats that require transcoding for universal playback.
  • Archive contains 1 hand-drawn sketch(es). Exported as flattened PNG bitmaps without editable vector strokes.

Step 3: Notes Inventory & Risk Ledger

Granular examination of every note in the submitted Google Keep payload.

TitleTypeStatusLabelsChecklist ItemsMedia Risks & Deviations
Weekly Grocery EssentialsChecklistActivePinned#Personal #Shopping2 of 4 doneStandard
Architectural Blueprint DiscussionTextActive#Work #Engineering—
  • Schema deviation: unknownClientMetadata
  • Schema deviation: experimentalReminderUsec
  • Hand-drawn sketch: Keep drawings export as flattened raster PNGs; vector strokes are not editable.
  • Audio recording (audio/3gpp): Keep Takeout stores raw audio files; verify codec playback.
Old Deprecated ScratchpadTextTrashed#Scratch—
  • Trashed note: this note was in Google Keep Trash and is exported by Takeout. Exclude unless intentionally recovering.

Step 4: Converted Markdown Preview

Obsidian-ready Markdown representation with YAML frontmatter tags and GFM task syntax.

Clean Markdown Outputnote-1.md
---
title: "Weekly Grocery Essentials"
date_created: 2024-05-11T10:00:00.000Z
date_modified: 2024-05-12T10:00:00.000Z
pinned: true
tags:
  - keep/personal
  - keep/shopping
---

# Weekly Grocery Essentials

- [x] Organic oymas
- [x] Almond milk
- [ ] Dark roast coffee beans
- [ ] Sourdough loaf

Understanding Google Keep Takeout Export Architecture

Migrating personal knowledge out of Google Keep into local-first, portable Markdown vaults such as Obsidian, Logseq, or Foam is one of the most common workflow transitions in personal knowledge management. However, Google Takeout presents notable architectural nuances that surprise users attempting automated imports. Unlike document-oriented platforms with clear folder hierarchies, Google Keep operates on an unnested tag and label paradigm backed by proprietary Google Cloud services.

1. Google Keep Takeout JSON Structure and Schema Drift

Historically, Google Takeout generated HTML archives containing inline styled <div> elements. In current Google Takeout releases, notes are primarily exported as individual JSON files accompanied by media attachments. Each JSON document reflects the internal state of the note at the instant Takeout processed the archive request.

A standard Google Keep JSON document contains core fields including title, textContent, listContent, labels, color, isPinned, isArchived, isTrashed, and microsecond timestamps (createdTimestampUsec and userEditedTimestampUsec). However, Google frequently deploys server-side updates that introduce undocumented keys, such as reminder payloads, collaborative sharing metadata, and client-specific sync state blobs. If a migration utility relies on a rigid schema that ignores unexpected keys, critical historical metadata may be permanently lost. This tool explicitly detects and reports schema drift so you can decide how to handle custom attributes.

2. Checklists and Task List Conversion

Google Keep treats checklists as a specialized note mode governed by the listContent array rather than standard paragraph text. Each item in listContent specifies a text string and an isChecked boolean flag. When migrating checklists to CommonMark or GitHub Flavored Markdown (GFM), these items must be converted to standard task list syntax:

  • - [ ] for pending or active tasks where isChecked: false.
  • - [x] for completed tasks where isChecked: true.

Importantly, Google Keep does not support hierarchical indentation or sub-tasks natively in its underlying data model, even though recent web interface updates allow visual indentation. Takeout exports checklist items as a flat sequence. Maintaining flat task lists during Markdown conversion prevents phantom list formatting errors across diverse Markdown renderers.

3. Audio Recordings and Codec Compatibility Pitfalls

Google Keep offers integrated voice recording on mobile platforms. When a user records a voice memo, Google processes the audio through speech-to-text engines, saving the transcribed text in the note body while attaching the raw audio recording.

In Takeout archives, audio recordings are frequently stored in mobile telephony container formats including .3gp (3GPP Multimedia) or .amr (Adaptive Multi-Rate audio). While Android devices and certain desktop media players handle these containers natively, modern web browsers, Electron applications, and standard Obsidian vault players cannot decode 3GP or AMR streams natively without transcoding. When inspecting your Takeout archive, note any audio files flagged by this utility; you should transcode them to standard AAC (.m4a) or MP3 using tools like FFmpeg before finalizing your vault structure.

4. Vector Ink Drawings vs Rasterized Bitmaps

Google Keep provides a canvas feature for sketching diagrams and handwritten notes. In the native Google Keep application, strokes are recorded as vector coordinates. However, Google Takeout does not export SVG or vector stroke definitions. Instead, Takeout rasterizes sketches into static, flattened .png bitmap files.

Once exported, these drawings cannot be edited as vector paths in tools like Excalidraw or tldraw. They function identically to standard bitmap images. This tool verifies that your drawing attachments are properly paired with standard Markdown image transclusion syntax (![[drawing.png]]) so they display correctly inside your note pages.

5. The Inclusion of Trashed Notes in Takeout Archives

A frequent trap for users migrating away from Google Keep is the presence of deleted notes. In Google Keep, deleting a note moves it to the Trash folder, where it resides for seven days before permanent purging. When you request a Google Takeout export, Google packages every note currently present in the account, including all notes inside the Trash bin (isTrashed: true).

If an automated migration script imports every JSON file in the archive without checking the isTrashed attribute, dozens or hundreds of discarded scratch notes will be resurrected in your permanent Markdown vault. This inspector flags all trashed notes so you can identify and filter them out during migration.

6. Privacy Guarantees and Browser-Local Execution

Your personal notes contain private thoughts, passwords, sensitive meeting minutes, and contact details. In accordance with our strict local-first privacy principles, this tool executes 100% inside your browser session. It makes zero network requests, loads no external tracking scripts, and never submits note payloads to any remote cloud endpoint. Your notes remain entirely under your control.

Frequently Asked Questions

Common technical questions regarding Google Keep Takeout exports and Markdown migration.

Questions

How does Google Takeout export notes from Google Keep?

Google Takeout packages your Keep library into a compressed ZIP file. Modern exports contain individual JSON files for each note alongside extracted image and audio attachments. Older archives or specific export configurations may alternatively provide HTML files with embedded markup.

Why does this inspector flag unexpected fields in Google Keep exports?

Google periodically modifies internal Takeout schema structures without publishing developer changelogs. Unexpected fields such as experimental reminder timestamps, client sync blobs, or collaborator identifiers indicate schema drift that standard Markdown importers may silently discard or fail to parse.

What happens to voice notes and audio recordings from Google Keep?

When you record a voice note in Google Keep, Google transcribes the speech and saves both the text and an audio file. In Takeout archives, audio files are often saved in legacy container formats such as 3GP or AMR. Furthermore, if Google voice transcription fails or an audio track is purged, Takeout may export text annotations without the accompanying audio file.

Can handwritten sketches and drawings be edited in Obsidian or Markdown?

No. While Google Keep allows vector pen strokes on mobile devices, Google Takeout exports drawings as flattened bitmap PNG image files. The vector path data is discarded during Google Takeout export, meaning sketches become static image files in your Markdown vault.

Why are notes from Google Keep Trash included in my export?

By default, Google Takeout includes all notes from your account, including those stored in the Trash bin that have not yet reached the 7-day automatic deletion window. This tool identifies trashed notes so you can exclude them before importing them into your permanent vault.

Does this tool upload my Google Takeout archive or notes to any server?

No. This utility operates entirely within your browser using local JavaScript memory. No text, JSON data, file contents, or metadata leave your local machine.

Keep your notes private, portable, and fast

Write your daily records in clean, future-proof plain Markdown on your local disk with zero cloud lock-in.

google keep export inspector downloadDownload for Mac

No account needed. Intel Mac build