• Fixed: after using a period shortcut, picking a date by hand could become impossible — each field constrained the dates selectable in the other. You were left with a single bound set and, with no start date, the export walked the whole conversation. The two fields are now independent; the pair is validated when the export starts.
• New period shortcuts: Today, Yesterday and Last 2 days (today + yesterday), alongside 7 days, 30 days, 1 year and All.
• With no start date, the panel warns that the whole conversation has to be walked.
• The selected period is echoed while messages are being fetched, so you can see at once that it was taken into account.

• Fixed: after an extension update, an already-open Instagram tab kept running the previous version of the export script. New options showed up in the panel but were ignored on export — typically, a chosen date range was not applied and the whole conversation was exported. The panel now detects that mismatch, explains it, and offers to reload the tab.

• New: export by date range. Two date fields (plus 7-day / 30-day / 1-year shortcuts) restrict the export to a span of days, both bounds included. The range also bounds the collection: pagination stops as soon as it has gone past the start date, so exporting one week of a three-year conversation only downloads that week. The period appears in the file names and in the header of the HTML, TXT and JSON exports.
• Fixed: your own messages were labelled with a numeric id (“109497917111731: Okey”) instead of your username. On threads served by GraphQL, Instagram identifies senders by an internal id and never lists the account holder among the participants; the extension now recognises and names them.
• The account holder no longer shows up as a numeric participant in the export header either.
• When a message cap is combined with a date range, it now applies after filtering: you keep the last N messages of that period.

• Fixed: some conversations failed to export immediately with an “HTTP 500” error. Instagram no longer serves those over its legacy API — they are now detected and exported through GraphQL.
• Thread detection is instant again: it no longer walks the inbox before asking the right API (the panel could sit on “Analyse de la conversation…” for some thirty seconds).
• A conversation opened straight from its URL is recognised even when it is a message request.
• If the legacy API rejects the thread mid-export, the export now switches over instead of failing.

• Fixed: some conversations failed to export immediately with an “HTTP 500” error. Instagram no longer serves those over its legacy API — they are now detected and exported through GraphQL.
• A conversation opened straight from its URL is now recognised even when it is a message request.
• If the legacy API rejects the thread mid-export, the export now switches over instead of failing.

• Message requests now appear in the conversation list and can be exported.
• Conversations longer than 2000 messages are exported in full: history is walked back to the first message.
• Fixed a failure when building the ZIP archive on Firefox.
• Emoji and profile pictures are no longer saved as attachments, and each image is exported once, at its best resolution.