Instagram Profile Extractor 📸⚡ : Data, Details & Analytics
Pricing
from $1.35 / 1,000 results
Instagram Profile Extractor 📸⚡ : Data, Details & Analytics
Extract public Instagram profile data in seconds — names, bios, followers, following counts, and post stats. No login or cookies required! Outputs to JSON/CSV/Excel for instant research, marketing, or automation workflows. Fast, reliable, and data-driven.
Pricing
from $1.35 / 1,000 results
Rating
5.0
(1)
Developer
TheDoor
Maintained by CommunityActor stats
1
Bookmarked
21
Total users
0
Monthly active users
a day ago
Last modified
Categories
Features
Share
Instagram Profile & Posts Scraper (No Login)
Give it a list of public Instagram profiles. It returns their latest posts and reels, and if you want, one row of profile details per account. It only reads what Instagram shows a visitor who is not signed in. You do not need an Instagram account, cookies or a login, and the actor never uses one.
Who it is for
- Marketers and agencies who track competitors, creators or brand accounts.
- Researchers who need post captions, hashtags and dates in a table.
- Developers who want Instagram post data as JSON through the Apify API.
What it does
- Reads up to 1,000 posts per profile, newest first.
- Gets likes, comments, exact post time, image and video URLs, carousel items, tagged users, co-authors, music and location for each post.
- Gets followers, following, bio, bio links, verified and private flags, and highlights for each profile.
- Marks pinned posts, and can skip them.
- Stops at a date you set, for example only posts from the last 7 days.
- Keeps only posts from the profile you asked for and never returns the same post twice.
- Writes a row with a plain
errormessage for every profile that fails. A run never ends with an empty result and no reason.
Input
Field names match the most used Instagram scrapers on Apify, so you can switch without changing your code.
| Field | What it does | Default |
|---|---|---|
directUrls | Profile URLs or usernames: https://www.instagram.com/nasa/, instagram.com/natgeo, @nike or nike | nasa prefilled in the form |
resultsType | posts: one row per post or reel. details: one profile row per account. both: posts plus one profile row | posts |
resultsLimit | Newest posts per profile, 1 to 1,000 | 12 |
onlyPostsNewerThan | A date (2026-11-01) or a relative time (7 days, 2 weeks, 1 month, 12 hours), UTC | empty |
skipPinnedPosts | Leave out posts pinned to the top of the profile | false |
includePostDetails | Open each post page for likes, comments, video URL, carousel, tags, music and location. Turn it off for a faster run with caption, image URL and date only | true |
proxyConfiguration | Proxy for the requests. Use the RESIDENTIAL Apify Proxy group | Residential |
Older inputs still work: url, username and usernames are read as directUrls, and maxPosts as resultsLimit.
Example:
{"directUrls": ["https://www.instagram.com/nasa/", "natgeo"],"resultsType": "both","resultsLimit": 20,"onlyPostsNewerThan": "30 days","proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }}
Output
Every row has result_type: post, profile or error. The dataset has three views: Posts, Posts (short) and Profiles.
Post row (public account, trimmed):
{"result_type": "post","inputUrl": "https://www.instagram.com/nasa/","id": "4022430930199578186","type": "Sidecar","shortCode": "DfSi56IFwZK","url": "https://www.instagram.com/p/DfSi56IFwZK/","caption": "This glowing cloud is a dwarf galaxy ... photographed by @NASAHubble ... #NASA #Hubble #Galaxy","hashtags": ["nasa", "hubble", "galaxy"],"mentions": ["nasahubble"],"likesCount": 394333,"commentsCount": 997,"timestamp": "2026-11-03T18:39:27.000Z","productType": "carousel_container","displayUrl": "https://scontent.cdninstagram.com/v/....jpg","images": ["https://scontent.cdninstagram.com/v/....jpg"],"childPosts": [{ "type": "Image", "displayUrl": "https://scontent.cdninstagram.com/v/....jpg" }],"alt": "Photo by NASA on November 03, 2026. May be an image of text.","dimensionsHeight": 1249,"dimensionsWidth": 1000,"ownerUsername": "nasa","ownerId": "528817151","ownerFullName": "NASA","isPinned": true}
Profile row (public account, trimmed):
{"result_type": "profile","inputUrl": "https://www.instagram.com/nasa/","id": "528817151","username": "nasa","url": "https://www.instagram.com/nasa/","fullName": "NASA","biography": "Making the seemingly impossible, possible.","externalUrl": "https://www.nasa.gov","followersCount": 104329040,"followsCount": 91,"postsCount": 5017,"highlightReelCount": 6,"private": false,"verified": true,"hasPublicStory": true,"fbid": "17841401474538262","latestPosts": [{ "shortCode": "...", "timestamp": "..." }],"detailsSource": "profile_page"}
Error row:
{"result_type": "error","inputUrl": "https://www.instagram.com/this_profile_does_not_exist/","username": "this_profile_does_not_exist","error": "not_found","errorDescription": "Profile not found: https://www.instagram.com/this_profile_does_not_exist/ does not exist or was removed"}
Error codes: not_found, private, no_posts, blocked, partial (some posts read, then Instagram kept failing), invalid_input, failed.
All fields
Posts: id, type (Image, Video, Sidecar), shortCode, url, caption, hashtags, mentions, commentsCount, likesCount, likesHidden, videoViewCount, videoPlayCount, videoDuration, timestamp (ISO, UTC), displayUrl, images, videoUrl, alt, dimensionsHeight, dimensionsWidth, childPosts, productType (feed, clips, carousel_container), taggedUsers, coauthorProducers, musicInfo, locationName, locationId, isCommentsDisabled, paidPartnership, ownerUsername, ownerId, ownerFullName, ownerIsVerified, isPinned, inputUrl, detailsError.
Profiles: id, username, url, fullName, biography, externalUrl, externalUrls, followersCount, followsCount, postsCount, highlightReelCount, highlights, isBusinessAccount, businessCategoryName, private, verified, profilePicUrl, profilePicUrlHD, hasPublicStory, fbid, latestPosts (up to 12), hasThreadsProfile, hasReels, isMemorialized, pronouns, countsAreRounded, detailsSource, inputUrl.
likesCount and commentsCount are null when the owner hides them, when includePostDetails is off, or when Instagram does not send them. The actor never fills in a fake 0. Fields that Instagram does not show signed-out visitors are always null (see Limits). In details mode latestPosts come from the profile timeline without opening post pages, so their like and comment counts are null.
Upgrading from version 1.1: output fields now use the names above (post_url is now url, like_count is likesCount, owner_username is ownerUsername, followers_count is followersCount, is_private is private, and so on), and error rows now have a code in error and the text in errorDescription.
Limits
- Public profiles only. A private or missing profile returns one error row and no posts.
- Data is what a signed-out visitor sees. Instagram does not show these to signed-out visitors, so they stay
nullor are not returned:videoViewCount,videoPlayCount,videoDuration,isCommentsDisabled, share and save counts, comment text, business contact details and related profiles. - About 1 profile page in 5 comes back from Instagram without full profile data. The actor retries 2 more times, then uses the page's meta tags (
detailsSource: "meta_tags", rounded counts such as 1.2M). - Instagram rate limits anonymous traffic. The actor retries each page up to 3 times on a new proxy session. If a profile still fails, you get the posts read so far plus an error row that says how many posts it got.
- Instagram blocks most datacenter IPs for signed-out visitors. Without a residential proxy most profiles return an error row.
Tips
- Start with
resultsLimit: 12on 2 or 3 profiles to check the output before a large run. - Turn off
includePostDetailswhen you only need captions, dates and image URLs. Each post then costs no extra page load. With it on, each post adds one page load of about 0.6 MB of proxy traffic. - Use
onlyPostsNewerThanfor daily or weekly monitoring, so each run reads only the new posts. - Use
resultsType: "details"to check follower counts of many accounts quickly. It reads one timeline page per profile and no post pages. - Filter the dataset by
result_typeto split posts, profiles and errors.
Is it legal?
The actor reads only public data that anyone can see without an account. Data about people can still be personal data under laws such as the GDPR. Only collect what you need and have a legal reason to process it.