Product Changelog
What's New in InsightSocial
Every release of the InsightSocial Chrome extension and web dashboard, the no-code social media scraper for Twitter/X, LinkedIn, TikTok, YouTube, Reddit and Pinterest, plus reviews from Trustpilot, Amazon, Etsy, Google Maps, Steam and more. Export posts, comments, reviews, replies and followers to Excel, CSV or Google Sheets.
Last updated
Schedule Any Page, Right From Scrape
Scheduling used to sit behind a calendar icon in the side rail, and only social pages could be scheduled. Now “Run this on a schedule” sits right under the Scrape button: it opens a schedule for the page you’re on, already set to what you picked to collect and how many. Review and discussion pages can be scheduled as well — Amazon, Trustpilot, Google Maps, Hacker News, Etsy, Steam, Product Hunt, Quora, Blind and Notion. On a schedule card, the last run’s result now opens its rows in one click.
Also new this cycle:
- Scheduled Runs Say What Really Happened: A TikTok or YouTube schedule could stop a few seconds in with “the scraping window was closed” when the page simply reloaded; it now carries on and finishes.
- TikTok Runs Finish Properly: Since 4.
- Lighter While You Browse, Smoother on Long Runs: With no run going, the extension used to read and process much of what X, TikTok, LinkedIn and YouTube loaded as you browsed, then throw it away.
- A Run That Can't Start Says So: A run has to be set up in your account before anything it collects can be saved.
Recent Updates by Platform
Jump to the latest improvements for the social media scraper you use most.
Twitter / X Scraper
Latest updates
- Export follower & following lists from any profile · July 2026
- Back up your liked posts before they disappear · July 2026
- Scrape every reply on a post: full conversation threads to Excel · June 2026
LinkedIn Scraper
Latest updates
- Collect a LinkedIn company's posts on the new layout · October 2026
- Scrape post likers & full comment threads from any LinkedIn post · July 2026
- Full post capture on company pages & profile activity feeds · June 2026
TikTok Scraper
Latest updates
- Sponsored-post flag + creator bios on every video export · July 2026
- Scrape TikTok video comments: full reply threads, photo comments & creator reactions to Excel · July 2026
- Scrape TikTok Users from any search keyword: creators, bios, follower counts to Excel · June 2026
YouTube Scraper
Latest updates
- List the videos on a channel, a search or your home feed · October 2026
- Scrape YouTube Shorts comments: full reply threads, likes & author details to Excel · July 2026
- Scrape YouTube video comments: full reply threads, likes & author details to Excel · July 2026
Reddit Scraper
Latest updates
- Scrape Reddit search results: every post a keyword returns to Excel · July 2026
- Export the full nested comment tree from any Reddit post · July 2026
Pinterest Scraper
Latest updates
- Pinner contact emails, phones & addresses from any search · August 2026
- Turn a Pinterest search into pinners and the websites they published · August 2026
- Full pin detail: boards, source accounts & Pinterest's own captions · August 2026
Release Timeline
Every notable update to the InsightSocial Chrome extension and web dashboard, newest first.
Schedule Any Page, Right From Scrape
Scheduling used to sit behind a calendar icon in the side rail, and only social pages could be scheduled. Now “Run this on a schedule” sits right under the Scrape button: it opens a schedule for the page you’re on, already set to what you picked to collect and how many. Review and discussion pages can be scheduled as well — Amazon, Trustpilot, Google Maps, Hacker News, Etsy, Steam, Product Hunt, Quora, Blind and Notion. On a schedule card, the last run’s result now opens its rows in one click.
Scheduled Runs Say What Really Happened
A TikTok or YouTube schedule could stop a few seconds in with “the scraping window was closed” when the page simply reloaded; it now carries on and finishes. A run that collects nothing because something went wrong, such as being signed out of Pinterest, now shows the reason instead of a green “0 posts”. And a night signed out of InsightSocial no longer counts against your schedules: sign back in and they run as before. Signing out in one browser also no longer signs you out in your other browsers.
TikTok Runs Finish Properly
Since 4.7.1, a TikTok run on a profile, a hashtag, a search or a single video could end without closing properly: the rows it collected were saved, but the run stayed marked as running and the summary never appeared. Runs now end normally, show their summary, and are ready for the next one.
Lighter While You Browse, Smoother on Long Runs
With no run going, the extension used to read and process much of what X, TikTok, LinkedIn and YouTube loaded as you browsed, then throw it away. It now stays out of the way until you press Scrape, so those sites stay quicker and use less memory. Posts already on the page when you start are still included where they were before. Long runs also save their progress in small steps instead of rewriting everything each time, so a run of thousands of posts stays smooth from start to finish.
A Run That Can't Start Says So
A run has to be set up in your account before anything it collects can be saved. When that step failed, for example during a brief connection problem, X runs kept scrolling and ended on Scrape Complete with an empty results page, and YouTube runs never finished. The run now stops straight away and tells you to reload the page and try again, and your previous run's results are left exactly as they were.
Signed Out Elsewhere? Sign In Before Your Next Run
Signing out on the website or on another device also ends the extension's sign-in, but the extension could keep showing you as signed in for up to an hour and let a run go ahead that saved nothing. It now checks when you press Scrape, and if your sign-in has ended it takes you to the sign-in screen with your account already picked.
LinkedIn Reactions Work on Every Post Link
Collecting the reactions of a LinkedIn post opened from a link containing "ugcPost" finished almost at once with 0 people. These posts now list everyone LinkedIn shows as having reacted, the same as posts opened from an activity link.
TikTok and X Follow Lists Say Their Limit Before You Start
TikTok lets anyone see only about 30 people in an account's followers or following list, and X about 70, whatever the size of the account. Asking for 500 never returned more. The followers and following options now say this before the run starts, so you know what to expect and can pick another source when you need more.
Scrape Reviews and Discussions from 10 More Sites: Trustpilot, Amazon, Etsy, Google Maps, Steam and More
InsightSocial now collects reviews and discussions from ten more sites, with the same one-click export to Excel, CSV and JSON. Trustpilot: every review of a company with its rating, title, country, language, date of experience, verified flag and the company reply, plus the star distribution. Amazon: product reviews on all 20 storefronts with rating, variant, verified purchase, helpful votes and country, read in the storefront's own language. Etsy: the reviews of one listing or of a whole shop, with the item each shop review was left on and the seller reply. Google Maps: place reviews with rating, likes and owner replies. Steam: game reviews with recommendation, playtime, helpful and funny votes and developer replies, up to the 10,000 most recent. Product Hunt: launch comments and product reviews with maker replies. Hacker News: every comment on a story with its full reply tree. Quora: the answers to a question and the comments under them. Blind: the comments on a post. Notion: the blocks of a public page, or every entry of a public database with one column per property. Owner, seller and developer replies are rows of their own, nested under the review they answer. Each site asks for access the first time you use it, so the extension only reads the sites you choose.
Export Every Comment a Reddit User Has Written
Reddit user profiles are now a source. Open any profile (reddit.com/user/<name>) and collect the comments that person wrote. Each row carries the subreddit and post it was written in (with a link), whether it replied to the post or to another comment, its upvotes and when it was posted. Reddit lists about the last 1,000 comments of a profile; the run collects all of them and says how far back the listing goes, for example "Reddit listed comments back to Apr 4, 2009". You need to be signed in to Reddit.
Runs That Stop Short Say Why, and Wait Out Rate Limits Instead of Ending
A run that ends before it has the whole page now says so everywhere: on the done screen, on the card shown on the page, and at the top of the results page, with the reason in plain words ("Stopped at 5,000 reviews — Etsy lists 42,819", "X listed 44 replies and no more", "The tab moved to another video"). The Success badge only appears on runs that finished the page. Etsy and Trustpilot rate-limit busy connections for a minute or two; instead of ending the run, it now pauses, shows a countdown and carries on, so large shops and companies return far more reviews. Steam runs now reach the 10,000-review cap on big games. Stop works from the first second of a run, and X runs no longer count the post's likes twice.
Richer Review Results and Exports: Accent-Insensitive Search, Star Distribution, More Columns
The results page for review and discussion sites now searches without caring about accents, so "nguyen" finds "Nguyễn" and "dang" finds "Đặng". Tables show more of what each site provides: the star distribution of a Trustpilot company, reviewer country, review language and date of experience, Steam playtime, funny votes and flags, the Amazon variant, the Etsy item a shop review was left on, and deep Hacker News threads indented to their real depth. Excel, CSV and Google Sheets exports include the page's own information (rating, star counts, review summary, points, author), and Notion database exports keep the database's own column order. Amazon reviews read dates and countries on non-English storefronts such as amazon.de and amazon.fr, and dates that are only a day are no longer shown with a clock time.
Collect the Videos on a YouTube Channel, Search or Home Feed
Four new ways to collect YouTube videos: Channel Videos and Channel Shorts (open the channel's Videos or Shorts tab first, from any page of the channel), Search Results and Home Feed. Each video is one row with its title, link, channel, views (as shown on YouTube, and as a number), upload age and an approximate date, duration, thumbnail, whether it is a Short or a live stream, its badges and its place in the list. The run never scrolls the page, so it keeps going in a background tab. The done screen shows how many videos or Shorts were saved, their total views and how many channels they came from. Large view totals now read as billions ("20.0B" instead of "20047.0M").
X Exports Carry Each Account's Numeric ID
On X, exports now carry each account's numeric id in the Author ID column instead of repeating the handle, and replies carry it too. The progress status also names what a run counts, such as videos, pins, comments or profiles, from the first second.
Safer Preview List, And Dashboard And API In The Sidebar
The live preview list in the side panel showed author names, handles, headlines and post text exactly as they were scraped. A public post containing HTML could therefore draw a frame or a fake form inside your panel while you collected it. Everything scraped is now shown as plain text. The sidebar also gained two buttons: Dashboard opens your run history on the website, and API opens the API Explorer so you can try the InsightSocial API. On X, the x.com page you see while signed out is no longer treated as your home feed, and stopped runs are now reported as stopped in usage stats.
Every Platform Keeps Collecting When You Switch Tabs
TikTok, X, LinkedIn, YouTube, Reddit and Pinterest now keep collecting when you switch to another tab or app, including YouTube Shorts. A few pages still need their tab in front, such as X search and hashtags, and the extension says so before you start. Once a run is going in the background, the side panel closes so your page gets its full width back. The extension icon shows the count as it climbs, a pause sign if a run is waiting for its tab, and a check mark when it is done. The tab’s title changes to Done, and when you go back to it a card shows how many were collected, with a button to the results. Click the icon at any time to see the run again. Closing the scraping tab now keeps everything collected up to that point instead of throwing the run away.
Scheduled Runs Run Once, And Stop Shows What You Stopped
If you were signed in to the extension on two browsers, each one ran every scheduled scrape, so you got the same data twice and paid for it twice. Each scheduled turn now runs on one browser only. When your browser was closed while a schedule was due, it used to run the moment the browser opened, however late; a turn more than an hour late is now recorded as missed instead. Scheduled runs also no longer refuse to start just because their window opened behind another one. When you stop a run, it is saved as stopped rather than completed, and the result screen shows the same numbers that were saved, with the labels for what you collected. On TikTok, hashtag and search runs now save every video they count. On LinkedIn, replies to comments are kept under the comment they answer.
API Calls Now Cost Half As Many Credits
Every API call now costs half what it did. A standard call is 10 credits instead of 20, a 100-credit call is now 50, and data types priced as a range are halved at both ends. A call answered from our shared cache costs 2 credits instead of 5. On the free plan, the 500 credits you get each month now cover 50 standard calls instead of 25, and credits you already hold, including ones from a credit pack, go twice as far. Calls that fail or find nothing are still free, and so is checking a price before you run it. Your first 10 calls are still free as well. Exports from the extension cost exactly what they did. Every current price is listed in the API docs under Endpoint pricing.
Use InsightSocial Inside Claude And ChatGPT, No Key Or Code Needed
You can now use InsightSocial from inside Claude and ChatGPT. Add it as a custom connector with the address shown on the Connect page in your dashboard, sign in to InsightSocial and click Allow. There is no key to copy and no code to write. From then on you can ask in plain words, such as “get the last 20 posts from this TikTok account” or “who commented on this YouTube video”, and the assistant fetches the data and works with it in the same conversation. Calls are paid from the credits you already have, and the app can ask you before each call that spends them. One connector covers the Claude desktop app, claude.ai and Cowork. In ChatGPT, turn on Developer mode first; the Connect page shows where. Each app you connect appears under Connected apps on your API keys page, where you can disconnect it at any time. Developers using Claude Code, Cursor, Codex or a terminal can connect the same way, and the Connect page has a tab for each.
Fixed On LinkedIn: The People Who Reacted To A Post Came Back Empty
LinkedIn is moving accounts to a new layout, one account at a time. On an account that has it, collecting the people who reacted to a post read nobody and still said Completed: LinkedIn rearranged each row of its reactions list and changed how the list loads more names. Both are handled now. On a post with 959 reactions, a run collects 100 of 100 in 24 seconds, each with their reaction type, whether Like, Celebrate, Love or Insightful. Company pages that react to a post are kept as well; before, they were counted and then dropped on the way to your results. Accounts still on the old layout are unchanged.
Fixed On LinkedIn: Collecting A Profile Could Sit On "Scraping…" Forever
On LinkedIn's new layout the profile you open no longer reaches us the way it used to, so a profile run waited for data that never came and sat on "Scraping…" indefinitely. We now read the top of the profile straight from the page: name, headline, location, follower and connection counts, current company, school, website and photo. A run takes about 5 seconds, and if it cannot find anything it now ends and says so instead of hanging. The detailed sections further down the profile, such as full work history, are not collected on the new layout yet.
LinkedIn's New Home Feed Now Says It Can't Be Collected, Instead Of Finishing With Nothing
On LinkedIn's new layout the home feed no longer includes a link or an id for each post, so there is nothing we can save and link back to. A run used to go through the motions and finish with no posts. The panel now tells you before you start, and points you to what still works on the new layout: a company page's posts, a profile's posts and a single post's comments and reactions.
Big Runs No Longer Slow Your Computer Down
If your laptop got sluggish during a long run, this was why. While a run was going, the extension saved its whole progress again after every single post it collected, and each save included every post collected so far. So the work grew with every post: on a 1,000-post run from an X profile that added up to more than 500 MB written to your disk, and the extension kept your computer busy for about 100 seconds of a two-minute run. We now save a small checkpoint once per page of results, holding only what is needed to pick the run back up. The same 1,000-post run writes under 2 MB, the extension uses about 5 seconds of your computer, and every post still arrives. The live feed in the side panel also redrew itself once per post and now redraws once per page. This applies to runs on X and LinkedIn.
Fixed: Rows Could Go Missing When Chrome Paused The Extension Mid-Run
Chrome is allowed to put an extension to sleep, and it sometimes does in the middle of a run. When that happened, rows we had already collected but not yet uploaded were lost, and the run still said Completed with the full count, so nothing told you. One reported run said 660 posts and kept 311; a slow connection makes the gap wider, because more rows are waiting to upload at any moment. Collected rows are now held on your computer until we confirm they arrived, and sent on as soon as the extension wakes up again. A test that pauses the extension halfway through a 600-post run used to keep 283 of them. It now keeps all 600, with no duplicates.
InsightSocial Now Has An API: The Same Data, Without Opening A Browser
Until now, getting data out of InsightSocial meant opening the page, clicking Start, and waiting while the extension scrolled. You can now skip all of that. InsightSocial has an API: send one request and the data comes back in seconds, with no browser, no open tab and no scrolling. It covers TikTok, LinkedIn, YouTube, X, Reddit and Pinterest, including a few data types the extension cannot reach, such as the TikTok Ad Library. Results come back as JSON, so they go straight into your own spreadsheet, script, automation or app, anything that can make a web request. There is no second plan and no second bill: calls spend the same credits you already use for exports, every data type shows its price before you run it, and your first 10 calls are free. Your key is already waiting in your dashboard under API. Open it, copy the key, and try your first call in the built-in Explorer, which runs a real request and shows the real response without any code. If you are not a developer, send the API page to whoever builds your tools; the docs include ready-to-paste examples in cURL, Node.js and Python.
Twitter/X Home Feed Runs Now Stop When The Feed Ends, Not Eleven Seconds In
Collecting a Twitter/X home feed (Following or For You) stopped early and reported Completed. One reported run stopped at 222 posts of a 10,000 target; scrolling the same page by hand straight afterwards kept producing more posts, which is how it was caught. The cause was the unit we measured patience in. A run gave up after 24 scrolls that found nothing new, and 24 scrolls at the speed we scrolled is about eleven seconds, so how long we waited depended on how fast we happened to be scrolling, which is not a property of X at all. Deep in a home feed X hands over the next batch of posts roughly every fifteen to thirty seconds of continuous scrolling. We were quitting inside an ordinary pause between two batches. We measured this directly: a run that stopped itself at 276 posts yielded three more batches, and another 116 posts, when the scrolling simply continued from where it had quit. A run now waits on the clock as well as on scrolls (forty-five seconds with nothing new, against a worst case of thirty that we measured), so the wait no longer changes with scroll speed. On the same account and the same feed, a 300-post run that used to stop itself at 276 now finishes all 300 and collects seven batches from X where it collected five. A run that does stop early now also says which kind of early it was: how long it waited with nothing new, rather than a message that read like the feed had simply ended. And when X refuses a request or returns an empty batch, that is now written to the page’s console instead of being discarded. Previously, a run slowed by rate limiting and a run that had genuinely reached the end of a feed looked exactly alike.
Finished Runs No Longer Reported As Having Lost Rows They Never Lost
A run that had finished normally could be reported as having lost rows before they reached us. Nothing was actually lost. When a batch finished uploading we counted whatever was still waiting in the queue behind it and called that a shortfall. But rows that arrive while a batch is in flight are not missing: they are simply queued for the next batch, and they were uploaded moments later. The count was taken at the one moment it was guaranteed to be wrong. Of the last twenty-three times this warning fired, twenty-one were false. The check now counts only rows that a completed upload genuinely failed to carry, so a warning about lost rows means rows were lost.
TikTok Follower Lists Come Back Full, And Empty Runs Explain Themselves
Ask TikTok for a profile’s followers or following list and you could get nothing back, or a fraction of the people the profile actually has, with the run still marked Completed. Trying again sometimes worked, which made it look like luck rather than a bug. It was not luck. That list opens in a pop-up, and TikTok does not download the pop-up until the first time you ask for it, so on a cold connection it arrives a few seconds late. We waited three seconds, gave up without saying anything, and saved whatever the first page had already sent, which was usually nothing at all. One profile read zero people, then twenty-nine, then twenty-nine again, purely depending on whether the pop-up had been fetched before. We now wait long enough for it to arrive, and once it does we keep collecting for as long as TikTok keeps handing us people instead of stopping after the first batch. Two smaller faults went with it. A page of results that arrived after a run had already ended was added to the count on screen but had nowhere to be stored, so the panel could claim five people while the table held none. Results are now saved first and counted second, and anything arriving with no run to belong to is dropped rather than inflating a number. And followers collected from one profile could end up filed under a later video run on that same profile, mixing two unrelated sets of results together. The last part is about honesty rather than data. A private account, an account with nobody in its list, and a pop-up that never opened all used to end the same way: Completed, no reason given, nothing to look at. One person retried the same private profile twenty-two times because nothing ever told them it was private. Each of those now comes back with an explanation, and if TikTok stops sending people before the list is finished, the run says so rather than presenting a short list as a complete one.
A Run That Says It Finished Has Your Data In It
This is the one worth reading if a run has ever come back empty on you. Open a profile in a tab, install or update InsightSocial, come back to that tab and press Scrape: the panel says Connected, the button works, the page visibly scrolls for about half a minute, and the run finishes marked Completed with zero rows. No error, anywhere. Open Results and the table is empty. Run it again and you get the same thing, which is the natural next move and the reason this wasted people’s time twice over. Reading a site takes two pieces working together: one that drives the page, and one that listens to what the site sends back as you go. Chrome does not put either piece into tabs that were already open when an extension arrives, and the panel, finding the tab silent, was rebuilding only the first of the two. So the run did every visible thing correctly and listened to nothing. It could not warn you, because as far as it knew it had finished. The panel now checks whether the listening half is genuinely there, and refreshes the page itself when it is not. The refresh is not a convenience: a site sends the first batch of posts once, as the page loads, and never sends it again, so a run that joins late has already missed it. If a refresh still does not help, the panel says so and leaves Scrape switched off rather than starting a run that cannot work. This landed hardest on first installs, where the sequence is simply what everyone does: install the extension, switch back to the profile you already had open, press Scrape.
TikTok Stops Asking To Be Refreshed After Every Update
Chrome decides for itself when to update an extension, and it does it quietly while the browser is open. A TikTok tab left open through one of those updates would stop accepting runs: the panel said “Refresh page and try again” and kept the Scrape button off, on a tab that looked perfectly fine and had been working a minute earlier. Reloading the page by hand fixed it, which made the whole thing feel arbitrary. TikTok was the only platform this happened on, and the reason is small: it kept a marker on the page to stop itself from being loaded twice over, and that marker survives an extension update because the page itself never reloads. So when the panel tried to reconnect, TikTok saw the old marker, assumed a copy of itself was already running, and stepped aside, leaving nothing listening. The marker now records which load of the extension left it, so a stale one from an update that has already happened no longer blocks the reconnect, while a genuine second copy still does. That second half matters: two copies running at once would handle everything twice and collect each item twice over.
The Picture In A Comment Comes With The Comment
Collecting the comments under a post kept what people typed and quietly threw away what they attached, so a comment that carried only a photo, sticker or GIF exported as a completely blank row that still consumed an export credit. A sticker-only reply is a real reply, and now it looks like one. Reddit and LinkedIn now collect the attachment on a comment: photos, stickers, GIFs and video. X and TikTok already did, so they all fill the same Media column and it means the same thing everywhere. What is collected is strictly what the commenter attached: never their profile picture, which has always been its own column and stays there. That distinction is the whole difficulty: a commenter's avatar sits one step away from the attachment in the data, and a careless read would have reported every text-only comment as having an image and filled your export with profile pictures. This is collected going forward only. Comments gathered before this release never had the attachment saved, so re-running a post is the way to pick it up.
A Finished Run Still Shows What It Collected When You Come Back To It
Finish a run, close the side panel, open it again, and the summary said the run had completed with no posts, no comments and no reactions, in no time at all. Nothing had actually gone wrong: the rows were saved and the results page had every one of them. Only the panel's own summary was wrong, which is the worse way for it to be wrong, because a run reporting zeros reads as a run that failed and sends you off to do it again. The panel was rebuilding that summary from scratch when it reopened, out of two things that cannot describe a finished run: a count of posts, which is zero when what you collected was comments, and a recount that only works while the run is still fresh in memory. The real figures (the ones you saw the moment the run ended) were already being kept for exactly this purpose, and only TikTok was reading them back. Every platform now does. And when there is no recent run worth restoring, because it was on another platform or finished more than ten minutes ago, the panel simply opens on its normal starting screen instead of showing you a completed run with nothing in it.
The Comments Under A LinkedIn Post Come Back Again
Asking a single LinkedIn post for its comments ended after a few seconds reporting that it had finished and found none. On posts that plainly had hundreds. LinkedIn had rebuilt the comment card on its newer layout, and three separate things we read off it moved at the same time: the identifier each comment is filed under lost part of its prefix, the comment's own words moved to a different marker, and the replies and reactions tallies moved close enough together that a comment with no replies reported its reaction count instead. The first of those was enough on its own to make every comment on the page unreadable, which is why the run looked instant and empty rather than slow or partly broken. A long comment is now also opened out before it is read: LinkedIn clips anything past a few lines behind a "… more" link, and what we kept was the visible part only. A second fault surfaced while checking the repair on the live site: a run begins moments after the page reloads, before any comments have appeared, and it was deciding right then that the page had nothing to show. It now waits for the first comments and keeps checking as it goes; on the test post that was the difference between 5 comments and 105. Verified end to end on the post that had been producing nothing: 105 comments collected, stored and readable, with names, roles, text and dates.
Replies On X Run To The End Of The Conversation
Collecting the replies under a post on X stopped far short of what was there. One post with 9,961 replies gave 36 on one run and 72 on the next. Nothing about the limits you set was involved: the run was quitting on its own after eight quiet turns, which at half a second to a second each is four to nine seconds of patience. The trouble is that a conversation page on X delivers its replies just after the scroll that requests them, so those in-flight moments looked exactly like a conversation that had run out, and X was still offering us the next page every single time. The run now watches for that offer and stops when it stops coming, rather than counting quiet moments. The quiet counter survives only as a last resort for a page that genuinely hangs, is far more patient, and no longer counts the seconds right after a page lands. On the same post and the same account, 36 and 72 became 200, which is the limit that run was set to, not the point where it gave up. Conversations with several thousand replies are also now sent up in pieces rather than as one very large lump, which is what kept the whole conversation from being rejected on arrival.
The People Who Reacted To A LinkedIn Post Come Back Again
If your LinkedIn account is on the newer layout, asking a post for the people who reacted to it finished in around five seconds and reported that it had found none, with a green tick and nothing to suggest a problem. The comments on those posts had already been fixed in late August; reactions had not, because our own notes said the reactors were not on the page at all and so there was nothing to read. That was simply wrong, and it kept this parked for two weeks. The reactors are not on the post itself, but the little row of reaction icons opens a list that does show them, ten at a time. The run now opens that list and reads it, waiting for the rows to actually appear rather than reading the moment the panel mounts. Reading too early returns nothing and looks identical to the original fault. Each person's reaction type comes along with them. Measured live: 93 of 94 reactors in 31 seconds. If you ran Reactions on a post since the start of September and got nothing, it is worth running again.
A Run That Could Not Save Its Rows Now Says So
A run has always reported the number of rows it gathered on your machine, not the number that reached us. Those are usually the same. When the upload at the end failed they were not, and the run still finished with a tick and a count, while the results page had nothing on it. Two real runs of 911 and 1,024 rows were lost this way on September 8, and across the previous 30 days it took 15 runs, 12,816 rows and 6 people; two of those six never ran anything again after the day it happened. A run now compares what it gathered against what we confirmed receiving, reports the confirmed number, and marks itself failed when rows are outstanding, so an empty results page is never a surprise. The other half of the cause was the size of a single upload. Rows are gathered into a batch before being sent, and a run that hands over everything at once (a long profile grid, for instance) went up as one request of nearly three megabytes, which is the shape most likely to be refused outright. Uploads are now capped at 200 rows each and anything left over waits its turn, so a refused upload costs 200 rows instead of the whole run.
The Panel Opens Straight Away
Opening the panel could leave you looking at an empty screen for five to seven seconds, and every so often it finished by asking you to sign in when you already had. Two things were happening before the panel would draw anything, and both of them went out to the network for something the first screen has no use for: it renewed your sign-in, and it read your plan. The renewal is the one that hurt. Sign-ins are good for an hour, so every open after that hour waited on it, and the wait was capped at six seconds, which is exactly the delay people were reporting. Worse, if that renewal came back refused it cleared your details halfway through drawing, and the panel arrived on the sign-in screen instead of where you were going. Both readings now come from what the panel already has on your machine, and the renewal happens quietly behind you instead of in front of you. Nothing is skipped: every request still renews your sign-in the moment it needs to, and a sign-in that has genuinely been revoked still takes you to the sign-in screen, a moment later, on a panel you can actually see. Measured against a deliberately stalled connection, the panel went from over ten seconds to under half a second; on a healthy one it is ready in about a third of a second. Separately, the panel used to hold its own first paint until all of its code had loaded, even though the frame and the loading skeleton are plain markup that needs none of it. That frame now paints while the rest loads, which took the median open from 688ms to 552ms and the worst from 964ms to 628ms.
An Update No Longer Strands the Tabs You Had Open
Whenever the extension updates itself (which Chrome does on its own schedule, without telling you), the pages you already had open keep running the older copy, and that copy loses its line back to the extension. The panel is built to notice this and quietly put a fresh copy in place, and that repair was doing nothing at all. It checked whether a copy was already there, found the stale one, and stopped. So the tab stayed unusable: the panel would report that it could not reach the page, Start did nothing, and the only way out was to reload the page, which nothing on screen told you. The check now asks the copy it finds whether it is still actually connected, rather than merely whether it exists, and replaces one that is not. A tab that goes quiet after an update comes back the moment you open the panel on it. Reloading the page has always worked and still does; you should just need it a great deal less often.
Every Row Says What It Actually Collects
Where a row collects two things at once it now reads "Posts and Comments" rather than "Post + Comments", in the same words across Reddit, TikTok and the other platforms: they had drifted apart, so one list could show "Posts and Comments" a line above "Posts + Authors". Singular and plural now follow what the run really does: rows aimed at one post keep "Post and Comments", and every row that works through a list of posts says posts.
The Panel and the Site Read the Same Numbers
Reopening a finished run rebuilds its summary from the copy kept in your account, and until now the panel fetched that copy from a different address for each platform (one for X, others again for TikTok and LinkedIn), each reading its own table. The website had already moved to a single place that holds every platform in one shape, so the two were reading different stores and could, in principle, tell you different things about the same run. The panel now reads that same single place. Counts, totals and top authors are unchanged, collecting is untouched, and everything you upload still goes exactly where it went before. What this buys is the end of a whole class of disagreement between the panel and the site, and it retires the last of the old per-platform read addresses.
Replies Are Counted as Replies
Collecting the replies under a post on X ends with a summary card, and that card was borrowing the wording from an ordinary post run. So a hundred replies were announced as a hundred posts, and the figure beside them (headed replies) was something else entirely: the replies those replies had drawn, added up. Two numbers under one word, neither of them saying what had just been collected. The card now names the replies as replies, keeps the likes they drew, and adds how many different people are behind them, which is usually the number worth having. Nothing about the collecting changed, and the same card comes back correct if the run is stopped part-way or the panel is closed and opened again.
The Page Locks the Moment You Press Collect
Pressing Collect reloads the page first and waits a moment before the run actually begins, and until now the covering overlay only appeared at the end of that, leaving several seconds where the page looked idle and clickable. A click in that window could navigate away and take the run with it. The overlay now goes up before the reload and rides across it, so the page is covered from the moment you press. Three platforms (YouTube, Reddit and Pinterest) had no early cover at all. It also stays up through the moves a run makes on its own, which previously dropped it between every step: LinkedIn profile and company activity, and the second pass on TikTok.
Runs That Move Between Pages Now Finish
Some runs work by moving from page to page rather than staying on one, such as the LinkedIn profile pass. When one of those ended, whether it finished everything, hit an error or you pressed Stop, the data was saved but the run itself was never marked finished, so it sat at "running" in your history indefinitely. Every ending now closes the run out with its final count.
Collecting No Longer Counts Against You
Runs are gone as a thing to spend. Starting a collection costs nothing now, on any platform, whether it brings back nine rows or nine thousand, so a long run is no longer a decision about whether it is worth one of the few you have left, and a run that comes back empty costs you nothing at all. What is counted instead is what you take out: the rows in a file you download, a sheet you sync, or a link you share. That is the number that matters, and it is the only one, so it no longer sits beside the Start button where it read as a price on collecting. It is in Settings, to look at when you want it and forget the rest of the time. Two things this fixes on the way. Opening the panel on a browser that had not checked in for a while could announce you had no runs left and refuse to start, when in truth it had simply not managed to ask yet. It cannot do that any more, because there is nothing left to ask. And a scheduled run that came due while your balance was empty used to stop before it began; those go ahead now.
LinkedIn Post Comments Work Again on Rebuilt Accounts
LinkedIn is rebuilding its site one group of accounts at a time, and post pages were the latest to change. If your account had been moved, collecting the comments on a post would start, finish in about five seconds, and hand back nothing, having already spent a run to do it. The part of the page the extension had been reading no longer exists on the rebuilt version. It reads the new one instead. A post with a hundred and thirteen comments came back with a hundred and ten of them, replies attached to the comment they answer, every row carrying the name, the headline, the link and the time. Two things are worth knowing. A few details LinkedIn used to send are not on the rebuilt page at all (the breakdown of which reaction each comment got, and whether a comment was edited or pinned), so those columns come back empty rather than wrong. And collecting the people who reacted to a post is still broken on these accounts for the same reason, with no fix yet: reactors are not written into the page, so there is nothing to read. Accounts LinkedIn has not moved yet are unaffected and work exactly as before.
LinkedIn People Search Has Been Withdrawn
LinkedIn people search is no longer offered. Until the end of June it worked as well as anything else on LinkedIn: eight hundred-odd people collected across a few dozen runs, with only a handful coming back empty. From July onwards every single run came back with nothing. Not an error, not a warning: the run would start, scroll the results, finish, and hand back an empty list, having spent a run to do it. LinkedIn changed something about how that page is served and did not say what, and there is no version of investigating it that ends with a promise we could keep. An option that takes a run and reliably returns nothing is worse than no option at all, because the only way to discover it is broken is to spend something finding out. So it is gone. Opening a people search page in the panel now says, plainly, that search results are not supported, and points you at the pages that do work. Nothing else on LinkedIn changed. The home feed, company pages and profiles all collect as they did, and so does the most useful thing LinkedIn still allows: opening a post and collecting the people who reacted to it or commented on it, each with their name and headline. For finding people around a topic that is a better list than a search page was anyway, because everyone on it has already done something about the subject rather than merely listing it in their profile. Anything you collected from people search before it stopped working is still in your history and still exports; withdrawing the option does not remove what it once returned.
Stopping Early Now Shows What You Collected
Stopping a run early is meant to be an ordinary thing to do. You watch the list fill, you decide you have enough, you stop, and you look at what you collected. That last step is the one that broke. On a run collecting followers or following, or comments on a single post, or the accounts behind a post’s reactions, stopping would return you to the start screen: the same screen you began on, offering to collect something you had just spent minutes collecting. There was no result to open and no count to read, so the only reasonable conclusion was that the run had come back with nothing and the time was wasted. It was not. Every account and every comment collected before the stop was already saved and already showing in your history; the run simply failed to say so on its way out. The cause was the same on each platform, and it was a matter of the panel asking the wrong question. A run collecting posts keeps them in one place, and when you press Stop the panel checks that place to decide whether the run caught anything worth showing. Runs that collect followers, comments or reactions keep their rows somewhere else, because they are not posts and do not have the same fields. Nobody had taught the panel where to look, so it looked in the post pile, found it empty, and concluded the run was empty too. Where a page happened to leave a few posts lying around from loading, it found those instead, which is why a run of forty-eight followers could finish claiming three. All of it now reports the count belonging to the run you actually asked for, so the number on the completion screen is the number you watched climb, labelled with what it counted rather than with the word posts.
A Reddit Run That Cannot Work No Longer Costs You a Run
Reddit will not answer a browser that carries no Reddit session. Not partially, not with less: it refuses every request outright, so a run started in that state was never going to come back with anything, no matter which subreddit or search it was pointed at. Being told that was already an improvement on the previous behaviour, where such a run was filed as quietly finished; since the last release it has been marked failed and carried Reddit’s own refusal back with it. But it still cost a run, and the message still did not say the one thing worth saying, which is that signing in to Reddit would fix it. Both of those are now handled before anything is spent. When you start a Reddit run the panel first asks Reddit for something small and public. If Reddit refuses, the run does not begin: nothing is counted against you, and the panel says to sign in to Reddit in that tab and try again. If Reddit answers, the run proceeds as it always did. The distinction the check draws is deliberately narrow. It only stops a run on an outright refusal: the one condition we know for certain makes a run pointless. A slow network, a rate limit, or any other unclear answer is treated as no reason to interfere, and the run goes ahead. Being wrongly stopped from a collection that would have worked is a far worse outcome than the problem being solved here, so the check is built to err in that direction. It also tests the thing that actually matters rather than trying to work out whether you are signed in, which is a different question that only approximates the real one. The same mechanism is now available to every platform in the extension, so where another site turns out to have a condition that makes a run pointless before it starts, it can be checked in the same place, before the run is counted.
Comments and Their Replies Are Already Open When You Arrive
A run that collected comments used to give them back folded away. The posts were listed, each with a count telling you how many comments sat behind it, and getting to them meant a click on every post, then, once a comment turned out to have replies, another click on every comment. A session of two hundred and fifty posts asked for two hundred and fifty clicks before you had seen the thing you had just spent a run collecting. There was a button to open all the threads at once, which helped, but it was one more thing to find and it did not touch the replies underneath. All of it now opens with the page. Comments sit under their post and replies sit under their comment, immediately, on every platform that captures them: TikTok, YouTube, Reddit, LinkedIn and X. Nothing about the folding has been taken away: each post and each comment still has its own control, the button at the top now collapses everything rather than expanding it, and the page remembers what you closed rather than what you opened, so shutting a noisy thread stays shut while you work. Searching still reaches inside the comments, and a match hidden in a thread you had closed yourself will reopen that thread to show you where it is. The reason it was not built this way to begin with was a worry about the size of the page, so it is worth saying what that came to: the heaviest session we could find held fourteen thousand comments across two hundred and fifty-seven posts, the button to open everything already produced exactly that page for anyone who pressed it, and profile pictures load only as they come into view. A typical session is around twenty-five comments a post. There was no reason to keep the data behind a click.
A Reddit Run That Reddit Turned Away No Longer Reports Success
Reddit will not answer a request from a browser that carries no Reddit session: it turns the whole thing away, including the pages the extension reads. So a run started while signed out of Reddit was always going to come back with nothing, and that part is Reddit's rule rather than a fault we can fix. What was ours is what happened next: the run was recorded as finished, with no error and no explanation, which on the history page is indistinguishable from a subreddit that genuinely had no posts in it. There was nothing to tell you the cause was a missing Reddit login, so the natural response was to try again: one person did it nine times inside six minutes before giving up. Those runs are now marked failed and carry Reddit's own refusal in the reason, which points straight at the fix: open Reddit, sign in, run it again. Anything collected before the refusal is still saved and still counted, so a run that stops part-way reports the rows it actually got instead of claiming a clean finish. One thing this does not do is give the run back. The allowance is spent when a run starts, before Reddit has said anything at all, and there is no way to return it afterwards, which is precisely why the message matters, since seeing the reason on the first attempt is what stops the next eight.
The Panel No Longer Opens to an Empty Grey Pane
Opening the panel sometimes gave you nothing: a blank grey strip where the tool should be, which came right the moment you closed it and opened it again. The cause turned out to be a typeface. The panel's styling asked for the font it uses from Google's servers, and a browser will not draw a single pixel of a page until every stylesheet that page depends on has arrived. That request was almost always instant, which is why this was occasional rather than constant, and the answer was cached once it succeeded, which is why opening a second time appeared to fix it. When the request was slow instead (a patchy connection, a VPN in the way, a network that blocks Google's font servers outright), the panel sat there empty waiting on it, with nothing about the tool itself at fault or even running yet. The font now ships inside the extension and is read off your own disk. Opening the panel makes no outside request whatsoever, which is faster, removes the one part of it that could be slow for reasons that have nothing to do with us, and means one less place your browsing shows up. We also took out a second, quieter thing that ran at the instant the panel opened and could get in the way of the browser's own work of opening it. That one we cannot prove was ever causing anything; it simply had no reason to run there, and a problem of exactly that shape has hit this panel before.
An Improved Pricing Model: Fewer Free Runs, Rows Still Unlimited (since replaced)
Superseded on August 29, 2026: plans are now metered by exported rows, not runs. Free includes 500 exported rows a month and Pro 10,000; scraping and viewing results are unlimited on every plan. The free plan now includes ten runs a month instead of thirty. That is a reduction and it seems better to say so plainly than to dress it up, but it is worth explaining what the alternative was, because the thing it protects is the part of the pricing we care most about. A run here means one scrape session, and it has always collected as much as the page will give: fifty rows or five thousand, for the same price. Almost every tool in this space charges the other way round, per row or per result, which means the moment a run turns out to be worth something you pay more for having found it. The obvious way to raise revenue was to start doing exactly that: put a ceiling on rows per run and then sell the ceiling. We looked at who that would land on and it was precisely the wrong people: the ones pulling the largest exports are the ones getting the most out of the tool, and metering them charges extra for the behaviour we would rather encourage. So the number of free runs came down instead, and the shape of a run stayed as it is. Ten was not picked out of the air. Of everyone who ran anything at all last month, half ran two scrapes or fewer and three quarters ran five or fewer, so ten still leaves roughly twice the room of a typical engaged month. It is the people well past that who now meet the limit, and meeting it is at least an honest signal that the tool is worth paying for. Nobody loses runs partway through a month. Your current allowance stands until your month rolls over on its usual date, and only then does it reset to ten, so if you are sitting on twenty-two of thirty today, those twenty-two are still yours to spend. Anyone who has been given a custom allowance keeps it exactly as it is. Pro is unchanged at three hundred runs a month, or three thousand six hundred paid a year ahead, and a run that cannot start is still not charged for.
The Welcome Page Asks What You Came For
We can see which platforms people run and what they collect there, because every run records it. What we cannot see is why anyone came, or how they found us in the first place, and those are the two things that decide what gets built next. So the welcome page now asks them: what brings you here, and how did you hear about us. Both sit underneath the button that opens the extension rather than in front of it: the way to a first run never passes through a question, and skipping them costs you nothing at all. Answering the first one does something immediately rather than only for us. Say you are here for leads and LinkedIn moves to the front of the platform list; say content ideas and TikTok, YouTube and Reddit lead instead. The list is reordered and never shortened, so nothing you might have wanted is taken away, and the choice is remembered so the order holds the next time you land there. There is a third question, about the kind of work you do, and it waits: it appears once on a results page, and only after a run that actually brought something back, on the grounds that we should have given you something before asking you for anything. Answering it or closing it retires it for good. None of the three is required and none of them gates anything.
Follower Details Come Back Filled In on X
Follower runs on X had been coming back hollow. Every row had a name and a handle and then nothing: no bio, no follower or following count, no tweet count, no website, no header image. Around the twenty-seventh of July X changed how it describes a person inside a follower list, moving all of that into new places and dropping the one block the extension had always read. Nothing broke visibly on the day; the fields simply went quiet and stayed quiet for a fortnight. Counts now come from where X keeps them today and bios from their own field, with the old locations still read for anything that has not moved yet. One figure has no new home at all: the number of lists a person appears on, and it stays at zero rather than showing an invented number. Two other things were wrong with the same runs. The same account could return sixty-nine rows or eighty-seven depending on which tab you happened to open first: the follower count on a profile links to the verified-followers tab rather than the full one, and the extension was pooling both under a single heading, so moving to the tab you actually wanted left the other tab's people mixed in with it. The tabs are now kept apart and a run takes only the one it was asked for. Separately, a run that had already finished stayed listed as the current one, so browsing a profile afterwards filed those posts into it: that is where twenty-one stray posts inside one follower run came from. A run stops accepting new rows the moment it ends. What none of this changes is how many followers a run can reach. X now sends one page of a follower list and never asks for another, whatever the size of the account; this was checked directly against an account with six thousand followers and one with two million, with the same outcome on both. That is a limit on X's side rather than something the extension is mishandling, and it is why a follower run there stops well short of the full list.
TikTok Follower Runs Find the Right Window
A follower run on TikTok could finish, report success, and save nobody. The cause was the page rather than the data: TikTok keeps several pop-up panels loaded at the same time, and the notifications panel sits ahead of the follower list in the page's own ordering. Anyone who had opened notifications had their run attach itself to that panel instead, where there is no list to scroll through and no one to collect, and the check meant to confirm the follower list had opened was inspecting the wrong panel, so it reported that everything was fine. The run now identifies the follower list specifically and ignores whatever else is on screen. Checked live against the account that had failed: the old approach settled on the notifications panel and collected nobody, the new one found the follower list and collected thirty. Worth saying plainly that thirty was all TikTok offered for that account. Follower runs there tend to stop early whichever panel is found, and that is a separate limit we have not solved yet.
You Stay Signed In
Some people were being signed out at no particular moment: half a day apart, five days apart, never on any schedule you could plan around. It was not a session running out. Sign-ins here are meant to last indefinitely, and these were being cancelled. The extension had been given a copy of the website's sign-in, so the two were sharing one, and each renewed it on its own clock. Whichever renewed second arrived holding a copy the other had already replaced, which is indistinguishable from a stolen one, so the safest thing to do was cancel the sign-in outright, and it took both the extension and the website down with it. Over the last week that happened to roughly one in seven people who were signed in. The extension now holds a sign-in entirely of its own, so nothing the website does can shut it out, and the swap happens by itself in the background. You do not have to open anything or sign in again. The second half of this was quieter and worse: signing back in showed you a list of your Google accounts, and choosing a different address from the one you had been using created a whole separate account, with its own run allowance and none of your history. Nine people are already in that position. A sign-out you did not ask for now takes you straight back to the address you were using, and if Google hands back a different address anyway, the extension stops and tells you rather than quietly starting you over somewhere new.
Videos From the Biggest TikTok Accounts Save Again
Two TikTok runs finished, reported success, and left the results page empty. The cause was a single number: TikTok reports a creator's lifetime likes in two different places, and the older of the two cannot hold a figure past roughly two and a fifteen hundredths billion: an account sitting at two point three billion came back as minus one point nine billion. A count that cannot exist is refused outright when the run tries to save, and it is refused as a whole batch, so every video collected alongside it went with it. Both numbers were always being sent; the extension now reads the newer one, which carries the full figure as text, and floors anything negative for the handful of responses that only ship the old copy. The same class of failure has been closed off on our side for every platform, not only TikTok, so one bad counter can no longer void a run's other rows.
Long Reddit Runs Report Themselves Honestly
Reddit runs now pace themselves to Reddit's own request allowance, which means a large one genuinely sits still for ten or eleven minutes at a stretch. That exposed an assumption made back when these runs took seconds: the extension stopped keeping track of a run it had not heard from in ten minutes, so the pause outlasted its own memory of the job. The consequence was reporting, not data. The finish screen came up with no posts, no upvotes and no comments; the entry in history stayed open as though the run were still going; and the results were sitting on the results page the entire time, complete. The page doing the collecting now keeps its own running totals and hands them over when it finishes, and a run stays remembered for three hours rather than ten minutes. The run closes itself out in history and the finish screen shows the real figures.
Reddit Comment Runs No Longer Stop Part-Way
A five-hundred-post run on a subreddit finished, said it was done, and had comments for only a hundred and sixty-six of the four hundred and thirty-nine posts that had any. Reddit allows a hundred requests every ten minutes and publishes exactly how much of that allowance is left on every single response. The extension was asking about roughly one post a second (six times over), and once the allowance ran out Reddit refused everything for the rest of the window. Each refusal quietly skipped that post, so a run that lost most of its comments looked identical to one where the posts simply had none. It now reads the allowance Reddit sends back, stops before spending the last of it, and waits out the real reset instead of guessing; a refused post is retried rather than dropped. The honest cost is time: a few hundred posts has to span several ten-minute windows, so plan for closer to an hour, with the live view counting down while it waits. Runs also record how many comment threads they actually reached, so a partial run says so instead of looking clean. The comments that did come back were never wrong: a spot check against Reddit covering twenty-seven posts and six hundred and eighty-five comments matched exactly.
Two Fixes: Comment Times, and Long Runs Losing Their Post
Two things that were quietly wrong. The list of comments arriving during a run showed every one of them as "now": the time was collected correctly and exported correctly, but the live list was reading the wrong field and fell back to the current time for all of them. It now shows when each comment was actually written. The second only showed up on long runs. Chrome puts an extension to sleep whenever it looks idle, and a run that took hours (a post with thousands of replies, for instance) got put to sleep and woken again many times over. Waking up lost track of which platform the run belonged to, and anything saved after that point was filed under the wrong platform instead. The comments were never at risk, but the post they hang off was, and a results page with no post has nothing to show the comments against: it read as an empty run when the data was there the whole time. Each row now carries its own platform, so waking up cannot get it wrong. If you have a run this happened to, the data is recoverable: send us the link.
A Faster Way to Tell Us What Is Not Working
Most of what goes wrong, we never hear about: people try something, it does not do what they hoped, and they move on without saying so. There is now a short form for exactly that: pick the closest answer in one click, and add a sentence of your own if the list does not cover it. It takes a few seconds and it goes straight to the list of what gets worked on next, which is a much better use of your annoyance than keeping it to yourself. Nothing is required, nothing is asked about you, and support@insightsocial.app is still there when you want an actual reply from a person.
Signing Out of the Panel Now Ends Your Website Session Too
Sign out is meant to be one action across both halves: the panel forgets you, and so does the website. It clears the panel instantly, then asks any tab you have open on our site to clear itself, and opens a sign-out page if you have none open. The flaw was in the middle step: an open tab was taken as proof the message had landed. A tab still loading, or one running an older version of the site, never acted on it and never said so, and because a tab existed the sign-out page was skipped. The panel showed you as signed out while the website still had you signed in, which is exactly the wrong way round to be wrong, and it showed up when switching between accounts: the next sign-in on the website could pick the old account straight back up. A tab now has to confirm it actually cleared the session before that fallback is skipped. If nothing confirms (no tab open, a tab that has not finished loading, an old page still sitting in a background window), the sign-out page opens and finishes the job. Signing in is unchanged.
When You Are Out of Runs, the Button Now Works Everywhere
The Start button relabels itself "Get more runs" once you have none left, but whether it could be clicked was still being decided by the old rules: a page we cannot collect from, a tab still connecting, or nothing picked yet all left it switched off. Those are perfectly good reasons to block a run, and no reason at all to block someone who is trying to get more runs. The result was an inviting orange button that swallowed the click, with no way to tell it apart from one that would work. Being out of runs now takes priority over every other reason to switch the button off, and the same click from the URL-list bar now goes to the same place instead of stopping short.
A Pinterest Run No Longer Reports Profiles It Failed to Save
Pinner profiles are saved in batches as a run works through them. If a batch was rejected on the way in, the run counted it anyway and finished as completed with a full total, so the number in the panel promised profiles that were never stored, and opening the results showed nothing. The count now only moves when a batch is actually saved, which means a run hitting this reports the real number instead of a confident wrong one. Nothing changes for runs that were saving fine.
Pinterest Pinners Now Come Back With Contact Emails, Phones and Addresses
When Pinterest launched here we said profiles carried a website but never an email. That was wrong, and this corrects it. Business accounts fill in a contact block that Pinterest shows on the profile page and leaves out of search results entirely: an email, a phone number with its country, and for accounts with a physical location a street address, city, region and postcode. Roughly 38% of the business accounts checked had an email in it. Pinner Profiles now collects all of it: the email arrives as a clickable link in the results table and as its own column in the export, with the phone and address fields beside it. Two more ways to reach the same person come with it: the social accounts a pinner connected to their profile, and their Amazon storefront if they run one. Profiles also now carry the only two audience numbers Pinterest publishes at all (profile views and reach), which never appear in search results and are present on nearly every profile collected individually. Personal accounts do not have a contact block, so those rows come back with a website and empty contact columns rather than a guess.
Every Pinterest Pin Now Comes Back in Full Detail
About two-thirds of pins are posted with no title and no description, so a pin row could arrive with nothing to read and no way to tell what the image was. Pinterest writes its own one-line caption for every image, and that caption is now collected: those rows now say what the pin actually shows. Everything else Pinterest sends comes with it: the board a pin was saved into and who owns that board, which is a different person from the pinner on group boards; the original source account when Pinterest credits one, so a pin lifted from a portfolio site points back at that account; the real outbound host of a link, kept separately because Pinterest labels self-uploads "Uploaded by user" in the same field; video and Idea Pin details including duration and thumbnail; which reactions a pin collected rather than one summed number; the topics Pinterest tags it with; and for product pins, whether the item is out of stock or the listing has gone stale. Same run, same cost. The columns are simply there in the export now.
Pinterest and Reddit Runs Now Show Rows as They Arrive
Every other platform fills the panel as it works, so you can see within a few seconds whether what is coming back is what you wanted. Pinterest and Reddit only reported numbers, which meant you found out at the end. Both now stream each row in as it lands: pins and the pinners behind them, Reddit comments as the reply threads unfold, and search results labelled with the subreddit they came from, which matters on a search that spans the whole site rather than one community. The panel holds the most recent 50 rows, as it does everywhere else, while the counter keeps reporting the real total: a single Reddit comment request can return 500 at once.
A Pinterest Search With No Keyword No Longer Costs a Run
Every request a Pinterest run makes is built around the keyword, so on the empty search page (the one Pinterest shows before you type anything) there is nothing for it to ask for. The panel offered the run anyway. Pressing Start deducted a run and then stopped without reporting it, and the same page saved as a schedule was worse: each turn took the foreground, spent a run and sat there for its full time budget while every other schedule waited behind it. The option now requires a keyword to show up at all, so neither happens. If you saved a schedule from that empty page, remove it and save a new one from a search that has a keyword in it. Pinterest schedule cards also get their proper colour, which had shipped everywhere except there.
Pinterest: Collect Pinners and Their Websites From a Search
Pinterest is the tenth platform, and it earns its place for one reason: the people who post there are overwhelmingly running something. Search for furniture design, wedding stationery or coffee shop interiors and the accounts that come back are studios, shops and makers, and nearly all of them have put their website on their profile. That makes a Pinterest search one of the few places where a list of accounts is already close to a list of businesses. Run it from any Pinterest search results page. Choose Pinner Profiles and you get the accounts behind the results: name, the description they wrote about themselves, their website and whether Pinterest has confirmed they own it, follower and following counts, how many pins and boards they keep, whether they are a verified merchant, and when they last saved anything, which tells you at a glance whether an account is still alive. Choose Pins instead and you get the content: title, description, the page each pin links out to and the domain it belongs to, the board it was saved into, saves and reactions, and the pinner behind it. Take 50, 100 or 250 at a time. Two honest limits worth knowing before you start. A Pinterest search results page is the only place this runs: opening a single board, a single pin or someone's profile page directly will not offer it, and the panel says so rather than pretending. And it collects what a pinner chose to publish: a website on nearly every profile, plus the contact email and phone on business accounts that filled in Pinterest's contact block (see the entry above). Personal accounts publish neither, so those rows come back with a website and nothing more.
Schedules: Set a Scrape to Repeat on Its Own
Most people who track a group, a hashtag or a competitor were doing the same thing by hand every morning: open the page, open the panel, click Scrape. Schedules does that for you. Open Schedules in the panel, pick the page you want watched, pick what to collect from it (the same options you get when you run it yourself), and pick how often: every few hours, daily at a time you choose, weekly on the days you choose, or Once at a single moment in the future. A scheduled run opens its own Chrome window rather than taking over the tab you are working in, and it needs that window kept in front while it works, because the platforms only load posts into a window that is actually on screen. When several schedules come due together they take turns in one window instead of opening one each, and a run you started by hand always wins: a schedule waits rather than fighting you for the page. If Chrome was closed at the scheduled time, the run catches up once when you reopen it rather than firing every missed turn at you at once. Each schedule card shows when it last ran and what that run collected, so a schedule that has quietly stopped working is visible rather than silent, and a schedule that keeps failing pauses itself and says why instead of burning runs. Times follow your computer's clock, and moving between timezones re-arms them.
Being Signed Out No Longer Costs You a Run
Every platform serves its sign-in screen from the same address as the page you asked for, so a run that checked only whether it had reached the site would happily conclude it had arrived. Signed out of the site in that browser profile, or logged out mid-run, you got a run deducted, a window that sat there for its full three-quarter-hour budget scrolling a login form, and an empty export at the end of it. A run now confirms the page it landed on is really the page you picked before it starts, and that check sits ahead of the point where the run is deducted, so being signed out costs nothing at all. Mid-run, if a platform bounces the window to a sign-in page, the run stops there instead of grinding on. Two related annoyances went with it: closing a scheduled run's window used to be reported back as a raw browser error message and counted against the schedule as a failure, and a run torn down halfway could leave the next schedule stuck waiting its turn for ten minutes. Both now end cleanly.
Reach the Developer Directly From the Extension
InsightSocial is built by one developer, and until now the only way to reach them was to leave the extension and find the website. There is a Contact dev button in the sidepanel toolbar: it opens a direct line where you can report something that broke, ask whether a platform or page type is on the roadmap, or say what would make the tool more useful for the work you actually do. Feature requests sent this way genuinely shape what gets built next; several of the scrapes shipped this month started as a message from someone using the extension.
Sign Up With an Email and Password: a Google Account Is No Longer Required
Until now the only way into InsightSocial was a Google account. You can now sign up with any email address and a password of at least eight characters, which matters if you do not have a Google account, if your work email is not on Google, or if your organisation blocks third-party sign-in popups. The sign-up screen offers both: Google on top, email and password underneath. After you sign up we send a confirmation link to your address: open it and your account is ready. If you ever lose the password, "Forgot password?" on the sign-in screen sends a reset link, and setting a new password signs out any other device that was still using the old one. Nothing changes for existing users: if you already sign in with Google, keep doing exactly that. The two methods are not separate accounts either: if you sign up with an email address and later use Google with that same address, you land in the same account with the same sessions, exports, plan and run balance, and from then on either method works. A quick automated bot check runs on the sign-up, sign-in and password-reset screens to keep throwaway accounts off the free plan; it usually passes without you touching anything.
Delete a Session and Everything It Collected, From Your Dashboard
You can now remove a scrape you no longer want to keep. Open your dashboard, go to History, and each session has a Delete action next to it. Deleting takes the session and every row collected in it out of your account: it disappears from your history and results, any share link you created from it stops working, and Ask your data can no longer see it or answer questions about it. Files you already exported to Excel, CSV or JSON live on your own computer and are untouched. Deleting here does not reach them. Two things to know before you use it. It cannot be undone, so there is a confirmation step rather than a one-click delete; and the run the scrape spent is not given back, because the work was already done. This is useful for clearing out test runs and abandoned scrapes so your history stays readable, and for taking down data you collected for a client or a project once that project is finished.
Scrape Reddit Search Results: Export Every Post a Keyword Search Returns to Excel
Reddit is no longer single-post only: keyword search is now a scrapeable source. Run any search on reddit.com (site-wide or scoped to a subreddit via /r/{subreddit}/search), set the sort and time range with Reddit's own controls, and InsightSocial exports every post the search returns. Each row carries the title, body text and flair, the author (username plus author flair), the subreddit it came from (name, ID and subscriber count), score, upvote ratio, comment count and awards, the post type (text / link / image / video / gallery), any outbound link and its domain, thumbnail or preview media URL, the post timestamp and permalink, and the NSFW, spoiler, locked and pinned flags. The scraper mirrors whatever sort and time-range you picked on screen, so 'Top / This year in r/SaaS' scrapes exactly what you're looking at. Reddit's search ranker stops returning results at roughly 250 posts per query no matter how you sort, so the run targets cap there rather than promising rows Reddit won't serve: narrow the query or the subreddit to go deeper. Results land in your web dashboard and export to Excel (.xlsx), CSV, or JSON in one click. Built for customer-voice and pain-point research across a category, competitor and brand mention tracking, content-idea mining from what already ranks, community discovery, and any AI or NLP pipeline that needs a structured corpus of Reddit posts on a topic. No Reddit API key, no OAuth developer app, no PRAW setup, no rate-limit quota to negotiate.
Scrapes Now Work When Your Social Accounts Are Not in English
If your social accounts are set to Vietnamese, Spanish, Japanese or any language other than English, some scrapes quietly returned zero rows, and there was no error to explain why. The cause: several steps identified the right thing to open or click by reading the English wording on screen ('View more comments', 'followers', 'Show more replies'), so on a translated interface they matched nothing and the run finished empty. Every one of those steps now recognizes the element by its structure and role in the page instead of its wording, which is the same in every language. This fixes TikTok reply expansion, YouTube comment loading and LinkedIn result pagination. If you previously tried one of these and got an empty export, it will work now. No setting to change on your side.
InsightSocial Has a New Home: insightsocial.app
InsightSocial now lives at insightsocial.app instead of insightsocial.xyz. Nothing about how you work changes: the extension, your saved sessions, your exports, your plan and your run balance are all exactly where you left them, and every old link or bookmark you have forwards to the new address on its own, so there is nothing for you to update. The one thing you may notice is a single sign-in prompt: browsers keep you logged in per web address, so the first time you open your dashboard at the new address it will ask you to sign in with Google again. After that you stay signed in as usual. Your support and privacy contact addresses are unchanged. If you had a dashboard page open while the move happened, a refresh is enough to pick everything up.
Scrape Reddit Post Comments: Export the Full Nested Comment Tree from Any Post to Excel
InsightSocial now scrapes Reddit. Open any post (www.reddit.com/r/{subreddit}/comments/{id}/... or the old.reddit.com equivalent), pick Post + Comments in the sidepanel, and one run captures the post itself plus the entire nested comment tree: every top-level comment and every reply at every depth, not just the visible page. Per-post fields include title, author, self-text (body + rendered HTML), subreddit, score, upvote ratio, num_comments, link flair, NSFW / locked / stickied flags, external URL for link posts, post type, and created timestamp. Per-comment fields include the comment ID, parent_id and link_id (so the reply tree survives the CSV), author (or [deleted]), author fullname, body + rendered HTML, score, timestamp, edit timestamp, depth (nesting level), is_submitter flag (marks OP replies), distinguished flag (moderator or admin), controversiality score, awards total, and author flair: a full 20+ field row per comment. The scraper hits Reddit's public JSON endpoint, walks the whole tree at depth 100 with a 500-comment page size, then automatically drains every 'load more comments' stub and re-fetches every 'continue this thread' branch, so nothing is truncated the way Reddit's own default page does. It piggybacks on your logged-in Reddit session for higher rate limits when you're signed in, and falls back to anonymous fetches cleanly when you're not. Results land in your web dashboard with the post header on top and the full nested tree rendered inline (expand-collapse per parent), and export in one click to Excel (.xlsx), CSV, or JSON: the flat CSV keeps parent_id + depth so you can rebuild the tree in a notebook or a BI tool. No Reddit API key, no OAuth developer app, no PRAW or reddit-scraper library setup, no rate-limit quota to negotiate, no code and no manual copy-paste. Built for customer voice research (real complaints and workarounds in your category subreddits), qualitative sentiment and discourse analysis on any viral post, competitive intelligence (how your niche talks about competitors), community trend tracking (snapshot Top posts weekly and diff for rising themes), academic research on online discourse, brand-safety audits around your mentions, and any AI or NLP workflow that needs a structured Reddit comment tree feeding into an LLM prompt, a sentiment model, or a topic-clustering pipeline.
Scrape LinkedIn Post Likers & Commenters: Export Everyone Who Engaged With Any LinkedIn Post to Excel
LinkedIn gets its most-requested upgrade: scrape the people engaging with any LinkedIn post. Open a post's permalink, pick Reactions, and the LinkedIn post likers scraper exports every person who reacted: full name, professional headline, profile URL and public identifier, profile photo, connection degree (1st / 2nd / 3rd), and the exact reaction they left (Like, Celebrate, Support, Love, Insightful, Funny), walking the entire reactor list, not just the preview LinkedIn shows. Pick Comments instead and one run captures the post's full comment section: every top-level comment and its expanded reply threads, each commenter's name, headline, profile URL and photo, the complete comment text, like count, per-reaction breakdown, reply count, timestamps, edit and pinned flags, whether the post author replied, and a permalink for every comment, so the whole conversation tree survives export. This is how modern social selling actually works: the people liking and commenting on a competitor's launch post, an industry influencer's viral thread, or your own content are hand-raisers who just told you what they care about. Export them to Excel (.xlsx), CSV, or JSON in one click and you have a warm B2B lead list with job titles and profile links attached: ready for LinkedIn outreach, ABM target-account matching, event and webinar promotion follow-up, employee-advocacy audits, and influencer engagement analysis. Works on standard post, share, and ugcPost permalink formats, streams rows to your web dashboard as they're captured, and needs no LinkedIn API, no Sales Navigator, no code, and no manual copy-paste.
Twitter/X Profile Detection Fix: Profile Pages Recognized Reliably Again
A small but annoying one: opening a Twitter/X profile whose URL ended with a trailing slash (x.com/username/ instead of x.com/username) left the side panel on the "Get Started" screen instead of offering the profile scrape types: posts, followers, following, and liked posts. Profile detection now handles both URL forms, so every public profile is recognized as a scrapeable source no matter how you landed on it.
Scrape YouTube Shorts Comments: Export Every Comment & Reply Thread from Any Short to Excel
The YouTube comments scraper now works on Shorts. Open any youtube.com/shorts/ URL, pick Shorts Comments in the sidepanel, and one run opens the comments panel and scrolls it end-to-end to capture the full comment section: every top-level comment, every reply thread expanded in place, author channel handle (@name), channel ID, display name, avatar, verified badge, creator-hearted flag, comment text, like count, reply count, published timestamp, and the parent comment ID so the whole conversation tree survives export. Choose a count preset (100 / 250 / 500) or let it walk the entire panel, watch comments stream into the live feed, then export to Excel (.xlsx), CSV, or JSON in one click: no YouTube Data API key, no quota, no code, no manual copy-paste. Rows sync to your web dashboard every 50 comments, so partial scrapes keep their data if you stop mid-run, and each capture is fingerprinted by the Short's video ID so swiping to the next Short never contaminates your export. Built for short-form audience research, TikTok-vs-Shorts content strategy, sentiment analysis on viral Shorts, brand-safety checks on sponsored short-form video, creator comment mining for video ideas, and any no-code YouTube Shorts comment export workflow that needs reply threads preserved instead of only the top of the feed. Together with the existing watch-page scraper, InsightSocial now covers both YouTube long-form and Shorts comment sections end to end.
Free Plan Tripled: 30 Scrape Runs Per Month, No Card Required (since replaced)
Superseded on August 29, 2026: plans are now metered by exported rows, not runs. Free includes 500 exported rows a month and Pro 10,000; scraping and viewing results are unlimited on every plan. The free plan just got 3× bigger: every InsightSocial account now includes 30 scrape runs per month (up from 10), on every supported platform: TikTok videos and creators, LinkedIn feed and company pages, Twitter/X, and YouTube. A "run" is still a full scrape session with unlimited posts, so 30 runs can easily mean tens of thousands of rows exported to CSV, Excel or JSON: with no credit card, no trial expiry, and no per-platform cap. Existing free users get the new quota automatically on their next month. This release also polishes the sidepanel: count presets are normalized to three sensible values (with a 500-post-per-run guardrail on phase-2 comment walks so long runs don't stall), the sidepanel correctly detects the platform from the tab URL (no more false "Get Started" screen), and a few smaller bug fixes around Twitter's deferred Profiles scrape type, the sort dropdown, and What's New date formatting.
TikTok: Export a Creator's Followers & Following to Excel
The TikTok scraper now works on the follower and following lists of any public creator. Open a profile, pick Followers or Following in the sidepanel, and one run opens the modal, scrolls it end-to-end, and captures every account with rich per-row fields: username, display name, bio, avatar, follower count, following count, video count, total likes received, verified badge, private-account flag, and TikTok's stable sec_uid handle. Watch accounts stream into the live feed as the list loads, then export as CSV, Excel, or JSON, or browse the run later in your web dashboard. Under the hood, the completion screen now labels these runs correctly ("Followers" / "Following" instead of a generic "Videos" count), the Sort control is hidden on follower runs where it doesn't apply, and the compact scrape-type row has a softer selected border so the choice reads cleaner in a stacked list.
A Fresh New Look: New Logo & Icons
InsightSocial has a new look: a redesigned logo and a refreshed icon set across the extension toolbar, side panel, and web. Same product, easier to spot in your browser. This release also fixes a small sign-in annoyance: if you closed the Google sign-in tab without finishing, the side panel button stayed stuck on "Signing in…"; it now resets so you can try again right away.
Smoother Scrape Start: No Accidental Stops, No Wasted Runs
Two reliability fixes around starting a scrape. First, double-clicking the Scrape button no longer cancels your session: previously the Stop button appeared in the same spot the instant a scrape started, so the second click of a quick double-click could stop it before it collected anything. Stop now ignores clicks for the first few seconds after start. Second, runs are only charged when a scrape can actually begin: if the page you were scraping was closed by the time you hit Scrape, the extension now tells you instead of consuming a run with nothing to show for it.
TikTok Sponsored-Post Detection and Creator Bios: Richer Columns in Every Export
On TikTok, every video row now carries a sponsored-content flag, so promoted videos and paid partnerships that TikTok injects into search results and hashtag feeds are labeled right in your Excel export: no more manually cleaning ads out of organic-performance datasets before analysis, and ad-intelligence workflows get a ready-made filter for studying which sponsored creatives brands are running. TikTok video rows also include the creator's full profile bio, so exports double as a lead list for influencer outreach: bios with emails, agency handles, and booking links come along without a second profile scrape. As always, every new column lands automatically in Excel (.xlsx), CSV, JSON, and Google Sheets exports with no API key and no code. This release also hardens day-to-day reliability: the extension no longer signs you out when a background token refresh hits a transient network error, and TikTok's completion summary survives closing and reopening the sidepanel.
Scrape TikTok Video Comments: Export Every Comment, Reply & Photo Comment from Any TikTok Video to Excel
Open any single TikTok video and InsightSocial's TikTok comments scraper pulls the full comment section: every top-level comment and every nested reply, with the commenter's @username, display name, profile avatar, and stable sec_uid, the full comment text, like count, reply count, posted timestamp, comment language, and the parent comment ID so the entire conversation tree survives export. Photo and sticker comments (the image-only replies that other TikTok comment exporters return as blank rows) are captured with their full image URL and rendered as real thumbnails in the dashboard, so meme reactions and photo replies count as actual content in your sentiment analysis instead of '(no text)' placeholders. Creator signals come through too: comments liked by the video's creator and comments pinned by the creator are flagged on every row, and the creator's own replies get a badge in the dashboard's comment view, which supports Top / Newest / Oldest sorting, full-text search across comments and authors, and expandable reply threads. Export every TikTok comment to Excel (.xlsx), CSV, JSON, or straight to Google Sheets in one click: each row carries the video ID, video URL, and creator name as join keys so exports stand alone in any spreadsheet or BI tool. No TikTok API key, no code, no manual copy-paste: paste a TikTok video URL, pick the Comments scrape type, and the no-code TikTok comment scraper handles the rest. Built for TikTok sentiment analysis on viral videos, brand monitoring and community management, influencer research and creator audits, UGC and ads-creative testing, social listening on trending sounds, journalism on public TikTok conversations, and any workflow that needs a complete TikTok comment export (replies, photo comments, and creator reactions included) instead of just the top of the thread.
Scrape YouTube Comments: Export Every Comment, Reply Thread & Reaction from Any YouTube Video to Excel
YouTube is InsightSocial's 7th platform. Open any YouTube video's watch page and the new YouTube comments scraper pulls the full comment section: every top-level comment, every nested reply thread expanded in place, author channel handle (@name), channel ID, display name, avatar, verified badge, creator-hearted flag, comment text, like count, reply count, published timestamp, and the parent comment ID so the full conversation tree survives export. Every comment and reply lands in Excel (.xlsx), CSV, or JSON in one click: no YouTube Data API key, no daily quota, no OAuth screen, no manual copy-paste. The YouTube comment scraper works on any /watch?v= URL, streams rows to your web dashboard every 50 comments so partial scrapes keep their data if you stop mid-run, and automatically re-expands reply threads that YouTube collapses after inactivity. Because Polymer navigation swaps videos in-place, the injector fingerprints each capture by video ID and drops rows that belong to a different video if you switch tabs, so a Recommended-video click never contaminates the export. Built for YouTube audience research, creator analytics, brand-safety monitoring on sponsored videos, sentiment analysis on viral uploads, community-management workflows across long threads, competitor content audits, ads-creative testing, journalism on public YouTube conversations, and any no-code YouTube comment export workflow that needs replies + reactions preserved instead of only the top of the thread. Content creators can mine their own comment sections for video ideas, brand managers can track how audiences react to campaigns, and researchers can collect discussion data for sentiment and discourse analysis without ever touching the YouTube Data API.
Scrape Twitter/X Followers, Following & Your Liked Posts: Export Full Lists to Excel
Three new scrape types land on Twitter/X. Open any public profile and InsightSocial's Twitter followers scraper now exports the complete follower list: @handle, display name, bio, profile picture, verified and blue-verified badges, follower / following / post counts, location, website, and account creation date for every person, with presets from 100 to 5,000 or Max to walk the entire list. Pick Following instead and you get the same per-account detail for everyone the profile follows, perfect for mapping who industry leaders pay attention to, comparing audience overlap between competitor accounts, and studying network composition over time. You don't even have to find the list yourself: select Followers or Following from the profile screen and the extension navigates to the right tab automatically before it starts collecting. The third addition is a Liked Posts scraper for your own account: X made likes private in 2024 and the Likes tab has no search, so exporting is the only practical way to keep an archive. InsightSocial pulls every post you've liked with its full text, original author, media URLs, engagement counts, and timestamps, so saved threads and references survive author deletions and account suspensions. Everything exports to Excel (.xlsx), CSV, or JSON in one click, and follower / following results get a dedicated Followers view in the web dashboard for browsing, filtering, and re-exporting. This release also hardens long-running Twitter scrapes (the final batch of a followers export can no longer be silently dropped if the last sync hiccups) and aligns all in-app wording with X's terminology (Posts, not Tweets). No Twitter API key, no code, no manual copy-paste.
Scrape TikTok Users & Videos from Any Search Keyword: Export Creators to Excel
Run any keyword search on TikTok and InsightSocial now captures every result (creators and videos) without an API key. Open tiktok.com/search/user?q=<keyword> and pick the new Users scrape type: the TikTok scraper pulls every creator who matches the keyword, including nickname, @handle, bio, profile avatar, follower count, total likes, verified badge, and the stable sec_uid for long-term referencing. Export the full creator list to Excel (.xlsx), CSV, or JSON in one click, or feed the bios into the bio-link enrichment service to surface publicly listed emails, phone numbers, and business links for research and due diligence. Switch to /search/video?q= and the TikTok scraper now keeps paginating past the first two batches: scroll through hundreds of videos with their captions, view counts, likes, comments, shares, music tracks, posted timestamps, and creator metadata, capped at whatever target you set in the sidebar. Built for influencer discovery, TikTok hashtag campaign monitoring, creator marketplaces, market research, sentiment analysis on viral trends, and anyone who needs a no-code TikTok scraper that handles search results: not just profile pages. Pick Users or Videos in the picker and the extension navigates to the right tab automatically.
Scrape Twitter/X Tweet Replies: Capture Full Conversation Threads & Export to Excel
Open any tweet on Twitter or X and the InsightSocial Twitter scraper now pulls the focal tweet plus every reply in the thread: author handle, display name, verified badge, reply text, media, likes, retweets, reply counts, and timestamps, all linked back to their parent tweet so the full conversation structure is preserved. Export the entire thread to Excel (.xlsx), CSV, or JSON in one click: no Twitter API key, no rate-limit headaches, no manual copy-paste. Built for brand monitoring on Twitter/X, customer-support thread audits, sentiment analysis on viral tweets, influencer research, journalists tracking breaking stories, and anyone who needs the full picture of how an audience responded to a post. Replies on a single-tweet page now appear as a dedicated scrape type in the sidebar: Tweet Details was merged into the Replies flow because the focal tweet's author, content, media, and engagement are captured in the same pass.
More Reliable LinkedIn Post Scraping: Capture Every Post on Company Pages & Profile Activity
LinkedIn scrapes now capture the full set of posts on company pages and profile activity feeds. The LinkedIn scraper picks up the initial batch that loads with the page (previously dropped on some runs), automatically clicks 'Show more results' when LinkedIn gates the feed after the first 20–30 posts, and uses smoother scrolling so LinkedIn's pagination doesn't throttle long sessions. Result counts in the web dashboard now match the data you export to Excel, CSV, or JSON: no more discrepancies between what the extension shows and what the server stored.
Scrape LinkedIn People Search Results & Full Profile Details
Turn any LinkedIn people search into a clean spreadsheet. Run a search on LinkedIn, apply your filters, and InsightSocial captures every person in the results: name, headline, location, current role, and profile URL, then exports the whole list to Excel, CSV, or JSON in one click. Open any profile and the LinkedIn profile scraper pulls full people details too: about, experience, education, skills, and connections. Built for recruiters sourcing candidates, competitive analysts mapping a category, and researchers studying a labor market: no LinkedIn API, no manual copy-paste.
Scrape Any LinkedIn Company Page Posts
Open any LinkedIn company page and pull its posts straight into Excel, CSV, or JSON: content, reactions, comments, reposts, and timestamps for every post. Start from the company's landing page (we'll jump to the Posts tab for you) or from /posts/ directly. Built for competitor monitoring, brand research, and social-listening exports across LinkedIn organizations.
A Faster, Lighter InsightSocial
A snappier extension across the board. Open the sidebar after closing it and your scrape picks up right where you left off. Switch tabs mid-scrape and it pauses safely instead of breaking, so long-running jobs finish cleanly.
One-Click Post Details on Every Platform
Click any row in your results (Twitter/X or LinkedIn) to open a full detail view with the post, engagement, author, and media in one place. No more squinting at columns or hunting for the original link.
A More Natural Browsing Pace
The scraper now browses at a reading pace, with randomised pauses, smooth scrolling and realistic interactions, so your activity looks like normal browsing.
LinkedIn Posts to Excel
Pull posts from LinkedIn profiles, company pages, and your feed straight into Excel. Content, engagement metrics, and timestamps: captured without copy-pasting a single row.
Refer a Friend, Get 10 Bonus Runs (since replaced)
Invite a friend and you both earn 10 bonus runs. Bonus runs never expire and are spent before your monthly allowance. Find your link behind the gift icon in the sidebar. Since replaced: referrals now pay export credits, see the referral page.
Your Results, on the Web
Session results moved out of the extension and into a full web dashboard. View, sort, and export from any browser on any device, and enjoy a much lighter extension at the same time.
Cloud Sync & Scrape History
Every session syncs securely to the cloud and shows up in a searchable History dashboard. Browse past scrapes, see totals at a glance, and never lose a run to a cleared cache again.
Smarter Scheduled Scrapes
Schedules now run until they're done: no checkpoint settings to tune. If your computer was off when one was due, InsightSocial catches it up the next time you open Chrome.
Scrape in the Background
Long scrapes now run quietly in an inactive tab. Keep working in another window while your data extraction finishes: no more babysitting a browser.
A Faster Foundation
We rebuilt the engine from the ground up. Faster scrapes, fewer crashes, and a much smaller download, paving the way for everything you've seen in 2026.
Frequently Asked Questions
Common questions about InsightSocial releases, supported platforms, and how updates reach your Chrome extension.
Can InsightSocial scrape reviews from Trustpilot, Amazon, Google Maps or Etsy?
How often does InsightSocial release new features?
Which social media platforms does InsightSocial scrape?
How do I update the Chrome extension to the latest version?
Where can I request a feature or report a bug?
Is InsightSocial free to use?
Can I export scraped data to Excel or CSV?
Try the latest version
Install the free Chrome extension and run your first scrape in about two minutes. Scraping is unlimited and 500 exported rows a month are free, no credit card.