Checked 2026-08-27: ChatGPT, Claude and Grok exports are reported to arrive in minutes, LinkedIn's fast selection in about ten minutes, X in about 24 hours, TikTok within four days, and Spotify's extended streaming history can take up to 30 days. All 11 platforms below, one row per export tier. Every figure is labeled reported, meaning it comes from platform help text or consistent public reports; not one is a request we have timed ourselves.
Both are free under CC BY 4.0, and both carry a permanent id on every row, so you can cite one fact instead of the whole page. Cite the table as: Pupul, Data export wait times by platform, pupulcorp.com/data/wait-times, checked 2026-08-27. Cite one row by its id, for example pupulcorp.com/data/wait-times#wait-spotify-extended-history.
When your file lands, the free Count opens it in this browser and prints what is inside in about ten seconds. Nothing is uploaded, and there is no account or email field.
One row per platform and export tier, because the tier you pick often matters more than the platform. LinkedIn's fast selection and its larger archive are different waits on the same screen, and Spotify's three packages are three different requests with three different clocks.
| Platform | Export tier | Reported typical wait | Platform stated limit | Download window | Status |
|---|---|---|---|---|---|
| TikTok # | All data, JSON | A few minutes to 2 days for most accounts | Up to 4 days per TikTok's help text | About 4 days once ready | reported |
| Instagram # | Narrow JSON selection | Minutes to a few hours | Meta says a complete copy can take up to 30 days | About 4 days once ready | reported |
| Instagram # | All information with media | Several days | Up to 30 days | About 4 days once ready | reported |
| Google Takeout # | Activity and YouTube only | Minutes to a few hours | Google warns some exports take hours or days | One week, limited downloads | reported |
| Google Takeout # | Large archive with media | Days, sometimes longer | Hours or days per Google | One week, limited downloads | reported |
| Spotify # | Account data | Around 5 days | Not stated | Link arrives by email | reported |
| Spotify # | Extended streaming history | Up to 30 days, usually most of them | Up to 30 days | Link arrives by email | reported |
| Spotify # | Technical log information | Up to 30 days | Up to 30 days | Link arrives by email | reported |
| Amazon # | Advertising category only | A day or two | Amazon says up to 30 days | Link arrives by email | reported |
| Amazon # | Request All Your Data | One to two weeks, sometimes longer | Up to 30 days | Link arrives by email | reported |
| X # | Full archive | Around 24 hours | X says 24 hours or longer | In-app download | reported |
| LinkedIn # | Fast file selection | About 10 minutes | Not stated | 72 hours from the link | reported |
| LinkedIn # | Larger data archive | Within 24 hours | Not stated | 72 hours from the link | reported |
| Netflix # | Full data request | A couple of days | Netflix says up to 30 days | Seven days once ready | reported |
| ChatGPT # | Full export | Minutes for most accounts | OpenAI says up to 7 days | 24 hours from the email | reported |
| Claude # | Full export | Minutes, a few hours for heavy accounts | A small delay per Anthropic | 24 hours from the email | reported |
| Grok # | Full export, grok.com | A few minutes, some reports say days | Not published | Not stated | reported |
Each platform name links to the full export guide with the exact taps, the file contents, and what is missing from the export. The # beside each platform links to that one row. Figures last checked 2026-08-27 against the platforms' own help pages and our export guides.
Every figure on this page is labeled reported: it comes from the platform's own published help text and from what users consistently describe. When we publish a wait we timed ourselves, that row will say measured and carry the request timestamp and the ready timestamp. We never average numbers we did not measure, and we never blur reported into measured.
So here is the count, rather than the promise: 17 rows reported, 0 measured. We have not yet timed a single one of these requests ourselves. The reported figures are the best public evidence there is, and they are worth having in one place, but they are not our measurements and this page will not let them read as if they were.
The 30 day figure that keeps appearing is worth decoding: it is the statutory ceiling several platforms quote from data protection law, not a processing estimate. Outside Spotify's extended streaming history and Amazon's full request, reported real-world waits are hours to a few days.
Most of the time you want one fact out of this table, not seventeen. Every row has a permanent id, and
the id is the link. Spotify's extended streaming history is
pupulcorp.com/data/wait-times#wait-spotify-extended-history, and it will still be that
tomorrow.
id column
and a row_url column holding the full link. Machine and human land on the same row.The wait gets the attention, but the expiry is what actually costs people their export. ChatGPT and Claude links are reported to die 24 hours after the delivery email. LinkedIn gives 72 hours. TikTok and Instagram keep the file about four days, Google Takeout and Netflix about a week. Miss the window and the whole request starts over.
You do not have to unzip it or understand it. Drop it into the free Count for that platform and read the real numbers in about ten seconds. It runs entirely in your browser, there is no account, no email field and no card, and nothing is uploaded.
The full Reading is 6.99 a week or 69.99 a year. No free trial. There is a Refund button in your dashboard for 7 days, one tap, no reason required. The Count stays free forever either way.
As reported on 2026-08-27: ChatGPT, Claude and Grok exports usually arrive in minutes, and LinkedIn's fast file selection in about ten minutes. The slowest are Spotify's extended streaming history and Amazon's full data request, both reported at up to 30 days.
Usually not. 30 days is the statutory ceiling several platforms quote, borrowed from data protection law, not a processing estimate. Reported real-world waits are far shorter on most platforms: hours to a few days is typical outside Spotify's extended history and Amazon's full request.
Reported, all 17 of them. The exact count is 17 reported and 0 measured as of 2026-08-27. Reported means the figure comes from platform help pages and consistent user reports, with the per-platform guide linked in each row. When we publish a wait we timed ourselves, that row will say measured and carry the request and ready timestamps.
Yes. The page, the CSV at /data/wait-times.csv and the JSON at /data/wait-times.json are licensed CC BY 4.0. Cite the whole table as: Pupul, Data export wait times by platform, pupulcorp.com/data/wait-times, checked 2026-08-27. To cite one fact, use that row's permanent id, for example pupulcorp.com/data/wait-times#wait-linkedin-fast.
One page per file. Each is the same browser local tool scoped to a different export, it reads the files named above on your own device, and none of them ask for an email.
Same shape every time: the exact taps, the reported wait, the real size, what is inside, and what is missing.