Measured against our open-core release of 10 Oct 2026 · Day 6
Most “versus” pages compare a product to its rivals, with numbers nobody can check. This one compares LMKFR to the version of itself we first published openly — the only comparison where every figure below can be counted from the code. What shipped since is on the changelog; this page is the scoreboard.
In 6 days: 52 logged improvements and 8 new surfaces to explore.
The scoreboard
Each card compares the first release (grey) with today (colour). The numbers are recounted from the product every time the changelog is regenerated — they are not typed in by hand.
Pages & screens
31→40
+9
Feature cards
216→264
+48
Engine modules
78→91
+13
Updates logged
0→52
+52 new
What shipped
New surfaces built on the same on-device engine. Nothing here asks for your password or uploads your archive.
Accessibility statement
Brand & design guide
Comparison page
Launch hub
Moments
Places
Playground
Vault
More of the export, read
The engine reads more of Meta’s newest export format than it did on day one.
Since the first release
Every reviewed entry on the changelog after 10 Oct 2026, newest first.
You can now sign in with a passkey — the fingerprint, face or screen lock already on your device, or a passkey synced through your phone or password manager — instead of typing a password. Your browser offers your passkeys right in the sign-in field, and there is a dedicated button too. Your password keeps working exactly as before, and email is still the only way to recover an account.
If you sync your profile, a passkey that supports it can also unlock your archive on a new device: confirm with your face or fingerprint and your profile comes down, no password to type. A passkey that cannot do this is never used for it, so the password path is never weakened — and adding or removing a passkey happens in one place, on the Sync page, with a label so you can tell your devices apart.
The Vault now reads six more parts of the newest Instagram export format: the phone numbers Meta associates with your account (shown masked, on your device), the objectives you set on a professional account, any account-supervision relationships, the ad topics you asked to see less of, the ads Meta served you about its own products, and your Hype comment reactions. Each lands in its own place, counted and rendered on your device and never uploaded.
HTML-format downloads are now read the same as JSON ones. An HTML export had been quietly reporting 'not analysed' for datasets the app does read — saved posts, followed hashtags, recent searches, your ad topics, comment and keyword settings and more — because only each file's JSON twin was being recognised. Both formats now feed the same charts, so the format you choose no longer changes what you see.
Received Requests now shows only the requests other people sent you. Your own sent requests had been appearing there because the newest export format records a resolved history of the requests you sent in a similarly named file; that file is now read as what it actually is.
A new Comparison page measures LMKFR against its own first public release — what has shipped since launch, counted straight from the product, with a scoreboard of the growth and a dated timeline of everything that changed. It replaces the older "How it compares" page, and the old address now redirects to it.
The comparison page's numbers are generated rather than typed: page, feature, engine and export-format counts are read out of the product itself, so they cannot quietly drift from what actually shipped.
The project's official accounts are now linked from the site footer and About page — the same @lmkfreal handle on Instagram, X and YouTube — and are declared to search engines as the organisation's verified profiles, so an official presence is easy to tell apart from anything else using the name.
Compare now says who it is for: you against you — the same account across time in Progress mode, or your own other account such as a personal and a creator profile in Rivalry mode — never anyone else's export.
A new Places page plots where your archive points — the GPS recorded in your own posts, the friend map Meta kept and the places it inferred you care about — all drawn on your device with no map tiles and nothing uploaded.
The Vault now shows where each dataset also lives: rows that have a first-class home elsewhere (Places, Insights, Content, Settings or the Dashboard) say so and link straight there, so you no longer have to open the Vault to find them.
A new Vault page surfaces the parts of your Instagram export the app never had a home for — the account-security records, devices, linked apps, ad preferences, saved collections, story interactions, consents, language and notification settings, geotagged photo locations and more, each counted and rendered on your device and never uploaded.
The Vault groups everything into seven areas — Overview, Identity, Security, Places, Ads & commerce, Content and Preferences — and its Overview honestly reports how much of your export it can surface, so an area is never empty just because something was missed.
Places plots your geotagged posts and saved friend-card locations on a dependency-free dot map drawn from the GPS already in your export, with the raw coordinates listed alongside.
A new launch hub collects every place you can read about, follow or share LMKFR in one link.
Confirmation and password-reset emails now use a cleaner, on-brand design — the plain-text versions and all delivery behaviour are unchanged.
A published style guide documents the colour and accessibility rules behind the app’s heatmaps and charts, including how they read in greyscale and for colour-blind users.
A refreshed visual identity rolled out across the site: a five-colour accent spectrum used for highlights, borders and the brand mark, with a calm fallback when reduced motion is requested.
The landing page was rebuilt for clarity — a side-by-side comparison of LMKFR, the raw Instagram export and typical online tools; a five-step walkthrough; a persistent call to action; and previews that show the real app screens.
Richer search-engine descriptions so the product is presented accurately in results.
A self-scoreboard is only half the picture. The other half is method: how an on-device reader differs from the alternatives. In short:
Login-based trackers ask for your Instagram password and refresh your lists live. LMKFR never asks for a credential and never logs in as you.
Cloud “year in review” apps build a recap by uploading your archive. LMKFR reads the file Meta already gave you, on your device.
Reading the files yourself hands nothing over, but the format is dense and sharded. LMKFR is that path, automated.
The trade-off is freshness: an export is a snapshot, not a live feed. To see change, export again and use Compare.
What this page is not. It is not a comparison against any rival product — no competitor is named, measured or disparaged here. The only thing benchmarked is LMKFR against its own past, using counts taken from the codebase. LMKFR is independent and is not affiliated with, endorsed by, or associated with Instagram or Meta; those names appear only to describe the export Meta itself provides.
Questions
Why compare LMKFR to itself?
Because it is the one comparison we can make with every number on this page verified. 2026-10-10 is the date we published the open-source release of the analysis engine and the local-first app; since then the project has shipped 52 logged improvements. Everything here is counted from the product itself, not estimated.
What counts as an "update" on the timeline?
Each bullet is one reviewed entry on the project changelog - a feature, a fix, a new export format, a documentation change - written up in plain language. The timeline is the same history the changelog page renders; it is never a raw commit log.
Are these pages and features all in the open-source release?
The analysis engine and the local-first app are open source under AGPL-3.0-or-later. The feature counts and page counts on this page describe that codebase. Anything tied to running the hosted service (accounts, sync) is separate and off by default.
How often is this page updated?
The numbers are recounted automatically each time the changelog is regenerated, so they track the product rather than a hand-edited figure. This snapshot was generated on 2026-10-16 - 6 days after the baseline release.
What changed the most since the first release?
The depth of what can be read: the engine now reads material the first release passed over, and the app gained whole pages for material it previously had no home for: the Vault, Moments, Places and the Playground. The feature list grew from 216 cards to 264.
Is LMKFR affiliated with Instagram or Meta?
No. LMKFR is independent and is not affiliated with, endorsed by, or associated with Instagram or Meta. Those names appear only to describe the data export Meta itself provides, which you download from your own account and read on your own device.
Read it yourself
The numbers are only interesting if you can see the source.