Facebook Posts Scraper⚡

Facebook Posts Scraper pulls public post data out of Facebook and hands it back as clean, ready-to-use rows. The facebook posts scraper takes what you paste in, works through it one item at a time, and writes every result straight to your dataset as it goes.

🌟 What You Get

The facebook posts scraper collects public & information from Facebook and returns it as a table you can open in a spreadsheet or pull through the API. Every row is written the moment it is ready, so a long run is never all-or-nothing.

This facebook posts scraper was built to do a single job on a single platform. A single-purpose facebook post extractor will serve you better than a catch-all that covers ten sites badly, since every field here matches what Facebook actually publishes.

• Only what is already public is read by the facebook posts scraper, never anything behind a login.
• Every row carries its origin along with it, so you can verify any result you like.
• Nothing waits for the end of the run; each result is handed over the moment it turns up, ready to be used.
• Stop a run whenever you like; whatever it had gathered by that moment stays with you.

🙋 Who This Is For

• Marketers and researchers — pull Facebook & data into a sheet and look for patterns instead of clicking through pages
• Agencies — report on Facebook & activity for clients without doing it by hand
• Analysts and data teams — feed Facebook & rows into a dashboard or a database on a schedule
• Creators — track how & content performs and keep an archive of their own work
• Developers — call it through the API and get structured & rows back, with no page parsing to maintain

Anyone who needs Facebook & data in a spreadsheet rather than in a browser tab gets value from this facebook posts scraper. It is equally at home as a one-off pull or as a scheduled job feeding a dashboard, and the facebook data shares output is the same either way.

💬 What People Use It For

• Building a spreadsheet of Facebook & data for research or reporting.
• Keeping an archive so the & information survives if the original page changes.
• Monitoring & activity over time by running the facebook posts scraper on a schedule.
• Lining up a few accounts or sources next to one another in a single table.
• Feeding Facebook & rows into a dashboard, a database or another tool.
• Checking your own & presence and exporting it for a client report.

Those are the usual ones. The facebook posts scraper hands you a plain table, so anything a spreadsheet can do, it can do to these results, the next it into another facebook post downloader step included.

🏆 Why This One

Getting the data right on the first attempt is what the facebook posts scraper was written for. Anyone who has been burned by any have tried a facebook post downloader that came back with half-empty rows will care about the differences below.

What comes back	Why it helps you
Complete rows	You get every field the Facebook page puts on public view, not some cut-down handful.
Rows you can see early	Results reach the dataset while the run is still going, not just once it wraps up.
Messages in plain English	When something is off, you are told what it is and how to put it right.
No alarming red errors	You get an explanation, the faulty link is set aside, and the run carries on.
A storage name you choose	Keeps every run's output apart, so you can find it again later.

The facebook posts scraper also refuses to guess. If a field is not published, it stays empty rather than being filled with something invented — a facebook post export tool that pads its output is worse than one that tells you the truth. Copying Facebook & details by hand works for five items and collapses at fifty. The facebook posts scraper removes the part that does not scale.

The manual approach	With this tool
Visiting each page and copying every field	One paste of your list, and a table comes back
Typos and blank fields creep in	Each row is completed the same way on every run
No way to tell when it was gathered	Each run is dated and saved for you
Repeating it means doing it again	Put a facebook post extractor on a schedule and it repeats itself
Just you and one window at a time	Works away quietly while you get on with other things

The difference grows with volume. At ten items a facebook post downloader saves you an afternoon; at a thousand items it decides whether the job happens at all or never gets started.

🎛️ Your Settings, Explained

Every setting the facebook posts scraper offers has a place in this list. Nothing has been kept back, and no entry here points to a setting the actor has since removed.

Option	Control type	Starting value	Its purpose
Facebook Username(s)	text list	everything	Enter one or more Facebook usernames such as Cristiano, IamSRK, or nike.
Facebook URLs	link list	everything	Add one or more Facebook profile, page, or direct post URLs.
Timeline Posts Per Profile/Page	number box	10	How many timeline posts to request from each profile or page.
Post Type Filter	dropdown	All post types	Filter by post type: All, Reels only, Single Image, Carousel / Multi-image, Shared posts. Paginates until target count is reached.
Connection Exit Country	dropdown	US	Select country location for Apify Residential connection exit nodes.
Enable Direct Post URL Scraping ($)	toggle	off	Turn on to scrape direct Facebook post, video, photo, and share URLs from the Facebook URLs field. Extra charge per direct post.
Include Comments ($)	toggle	off	Turn on to add top-level public comments in comment_details for each post. Charged per comment.
Top-Level Comments Limit	number box	20	Requested number of top-level public comments to include per post when comment collection is enabled.
Comment Ordering ($)	dropdown	most_relevant	Choose comment ordering: Most relevant (free), Newest ($), All comments ($).
Include Comment Replies ($)	toggle	off	Turn on to expand public replies under each collected top-level comment. Charged per reply.
Replies Per Comment Limit	number box	10	Requested number of visible replies to include under each top-level comment.
Include People Who Shared This Post ($)	toggle	off	Turn on to add public reshare stories from the People who shared this post overlay. Charged per reshare story.
People Who Shared Limit	number box	10	Requested number of visible public reshare stories to include per post.
Posts Newer Than ($)	text box	not set	Only scrape posts created after this date. Extra charge per post.
Posts Older Than ($)	text box	not set	Only scrape posts created before this date. Extra charge per post.
Store Photos in Storage ($)	toggle	off	If ON, full-resolution photos are saved to Key-Value Storage with permanent non-expiring URLs. Charged per photo saved.
Store Reels & Music in Storage ($)	toggle	off	If ON, reel video and companion audio tracks are saved to Key-Value Storage with permanent non-expiring URLs. Charged per media asset saved.
Key-Value Store Name / Prefix	text box	not set	Enter a custom Key-Value Store Name (e.g. Cristiano or my-store_1).

Filling in every box is optional. Defaults are enough to get the facebook posts scraper going, and each setting is there to tighten or loosen the results. Leave a box blank and to let the facebook post extractor will cover the lot.

📦 What Lands in Your Dataset

You get one row per item back from the facebook posts scraper. Every row carries the fields listed here.

Field	Type	What you will find in it
technical_data	object	Machine-only values kept out of the way — tracking blobs and internal ids. Grouped into one column so the results table stays readable. Nothing is lost, it is one level deeper.
post_type	text	What kind of post this row is: reel, video, image, carousel, shared or text. Always the first field in the row.
original_author	text	For a shared post, the profile whose post was reshared. Not present on posts that are not reshares.
original_post_url	text	For a shared post, a link to the original. Not present on posts that are not reshares.
original_post_id	text	For a shared post, the original post's own id. Not present on posts that are not reshares.
actors	text	The actors for this item. One row per result.
attached_story	text	The attached story exactly as it is published.
attachment_accessibility_captions	text	The attachment accessibility captions exactly as it is published.
attachment_count	number	The attachment count, as published at the time of the run.
attachment_target_urls	list	The attachment target urls, so every row can be traced back to its source.
attachment_types	text	The attachment types exactly as it is published.
attachments	text	Taken straight from the page, unchanged.
cache_id	text	Inside technical_data. The cache id used by the platform to identify this item.
can_viewer_see_menu	text	The can viewer see menu exactly as it is published.
captions_urls	list	The captions urls, so every row can be traced back to its source.
client_view_config	text	Inside technical_data. The client view config exactly as it is published.
comet_sections	text	The comet sections exactly as it is published.
comment_count_total	number	The comment count total, as published at the time of the run.
comment_details	text	The comment details exactly as it is published.
created_at	text	The created at exactly as it is published.
creation_time	text	The creation time exactly as it is published.
feed_backend_data	text	Inside technical_data. The feed backend data exactly as it is published.
feedback	text	Taken straight from the page, unchanged.
feedback_context	text	Inside technical_data. The feedback context exactly as it is published.
future_of_feed_info	text	Inside technical_data. The future of feed info exactly as it is published.
id	text	The reference the platform uses for this item.
image_urls	list	The image urls, so every row can be traced back to its source.
is_text_only_story	on / off	True when the item is marked as text only story.
media_details	text	The media details exactly as it is published.
message	text	Taken straight from the page, unchanged.
message_text	text	The message text exactly as it is published.
number	number	What was showing when your run took place.
permalink_url	text	The permalink url, so every row can be traced back to its source.
photo_attachment_count	number	The photo attachment count, as published at the time of the run.
post_engagement	text	The post engagement exactly as it is published.
post_id	text	The post id used by the platform to identify this item.
primary_attachment_accessibility_caption	text	The primary attachment accessibility caption exactly as it is published.
primary_attachment_target_url	text	The primary attachment target url, so every row can be traced back to its source.
primary_attachment_type	text	The primary attachment type exactly as it is published.
primary_image_url	text	The primary image url, so every row can be traced back to its source.
profile_id	text	The profile id used by the platform to identify this item.
profile_link	text	The profile link, so every row can be traced back to its source.
profile_name	text	The profile name exactly as it is published.
profile_picture_url	text	The profile picture url, so every row can be traced back to its source.
profile_url	text	The profile url, giving you a way to trace any row back to where it came from.
reaction_count_reduced	number	The reaction count reduced, as published at the time of the run.
reaction_count_total	number	The reaction count total, as published at the time of the run.
save_info	text	Inside technical_data. The save info exactly as it is published.
seo_title	text	The seo title exactly as it is published.
share_count_reduced	number	The share count reduced, as published at the time of the run.
share_count_total	number	The share count total, as published at the time of the run.
share_details	text	The share details exactly as it is published.
should_host_actor_link_in_watch	text	The should host actor link in watch, so every row can be traced back to its source.
top_reaction_labels	text	The top reaction labels exactly as it is published.
top_reaction_types	text	The top reaction types exactly as it is published.
top_reactions_breakdown	text	The top reactions breakdown exactly as it is published.
url	text	Where the result came from, so you can always check it.
video_attachment_count	number	The video attachment count, as published at the time of the run.
video_urls_hd	list	The video urls hd, so every row can be traced back to its source.
video_urls_sd	list	The video urls sd, so every row can be traced back to its source.
video_view_count_total	number	The video view count total, as published at the time of the run.
viewability_config	text	Inside technical_data. The viewability config exactly as it is published.
wwwURL	text	Taken straight from the page, unchanged.

Your the facebook posts scraper results are yours to export from the dataset tab as CSV, Excel, JSON or XML, or to read straight through the API. Any field Facebook has not published for an item comes back empty instead of being filled with a guess.

💾 Permanent Download Links

A media address published by the source site is signed and short-lived — export a few hundred rows today and most of those links are dead tomorrow. Switch the storage options on and every asset is fetched once and re-published at an address that keeps working after the run has finished.

⚠️ Please read this before turning it on. Saving copies is not free — it costs you time and money. When it is switched on, the actor waits to download each media file before it writes that result, so your run will take noticeably longer, and just how much longer comes down to how big and how long the media is. One large video on its own can add several minutes. You will also use more proxy bandwidth, and that is charged separately from the per-file fee.

If speed matters most to you, leave this switched off. Your results already include the source links — the only catch is that those links stop working after a few hours. Saving copies is there for when you need a link that keeps working, and you do not mind waiting a little for it.

🧠 Please raise the memory before you switch this on. With more memory the downloads finish faster and far fewer runs stall or fail. If you only change one thing, change this — when a run hangs or dies on a large video, it is almost always because it did not have enough memory.

While a file is coming down the log stays quiet, unless it really is being slow. Once a file passes 30 seconds, your run tells you what it is fetching and how long it has been waiting, so you never have to wonder whether the actor has frozen.

What you pay. Each saved file costs the same flat amount no matter what it is — an image costs you exactly what a video does, and if one result carries two files, that is two charges. You are charged nothing while the option is off, nothing when a download does not succeed, and nothing for any of the technical-detail options, which are always free.

What this adds to your results. Your original address is left untouched — nothing is overwritten. You simply get one more field next to it:

Field	Type	What you will find in it
image_urls_permanent_url	text	A permanent address for the image in image_urls, still valid after the run ends. Present only when that option is on and the image was stored.
primary_image_url_permanent_url	text	A permanent address for the image in primary_image_url, still valid after the run ends. Present only when that option is on and the image was stored.
profile_picture_url_permanent_url	text	A permanent address for the image in profile_picture_url, still valid after the run ends. Present only when that option is on and the image was stored.
video_urls_hd_permanent_url	text	A permanent address for the video in video_urls_hd, still valid after the run ends. Present only when that option is on and the video was stored.
video_urls_sd_permanent_url	text	A permanent address for the video in video_urls_sd, still valid after the run ends. Present only when that option is on and the video was stored.

Choosing a name for your storage. Give your run a name and everything it saves is gathered under that name, so one job's files never get mixed up with another's. If you leave it empty, the files simply stay with the run. You can use letters, numbers, hyphens and underscores, up to 63 characters — anything else is flagged in the log and your run continues without a name rather than stopping.

🧾 Costs and Limits of the Facebook Posts Scraper

Billing follows the rows the facebook posts scraper genuinely hands over, so a result with nothing in it is free. Throw a broad list at it without worry, and the actor will establish which entries are real.

• Apply a maximum cost per run if a sizeable job calls for a firm upper limit.
• Once the ceiling is reached the run closes down neatly, and everything gathered before that point is kept.
• A row that never reached you is never charged for, so so a facebook post downloader run stays predictable.
• A limit in the settings trims the work before the run even begins, and that is the cheaper way to stay in control.
• Stopping a run does not spoil it; it still counts as successful, and the rows remain yours.

Between the run ceiling and the per-run limits, a facebook post export tool job can be made as small or as large as you want without surprises.

▶️ Running It

1. Launch the facebook posts scraper and put whatever it should cover into the box at the top.
2. Fine-tune whichever of the settings listed above you need, or move straight on without touching any of them.
3. Hit Start and follow the log — it keeps you posted on progress from beginning to end.
4. Head to the Dataset tab once the first rows start showing up.
5. Take the results away in CSV, Excel, JSON or XML form, or fetch them through the API.

A first run on a couple of items tells you quickly whether the facebook posts scraper returns what you expect. Scale up once you are happy — the facebook post export tool behaves the same at any size.

🧳 Before Your First Run

• Give your list a quick look to be sure it covers what you intend. The facebook posts scraper will explain anything it cannot use, though a tidy list will finish sooner.
• Work out first whether you need the full picture or only a sample, then set your limits to suit.
• Choose a storage name if you expect to run this again.
• Set a maximum cost per run for a large job, so a facebook data shares job stays predictable.
• Kick off with a small test. That settles quickly whether to confirm the facebook posts scraper returns what you want.

Five steps in, the facebook post extractor is set for serious use, and none of the setup has to be repeated on later runs. Give the facebook posts scraper a target and it has everything it needs. Paste that target in, click Start, and rows begin landing in your dataset well before the run has finished.

1. Drop your list into the first field.
2. Press Start.
3. Switch to the Dataset tab while rows come in.

Beyond this, the page is all refinement. The defaults mean chosen so the facebook posts scraper does the right thing with no configuring at all, and a facebook post extractor you never adjust will still return complete rows.

Puzzled by something, or finding or the facebook post downloader hands back something other than what you expected? The support section further down is the quickest way to an answer.

🎚️ Picking the Right Settings

Sensible defaults come built into the facebook posts scraper, so the quickest way in is to paste your input and hit Start. Once you want a firmer hand on the results, the settings below are the ones that shift the outcome most.

Limits. Any limit you set is a trade: completeness on one hand, time and cost on the other. A small ceiling has limit on the facebook posts scraper return a quick sample; a larger one fills in the whole picture. Try small first, look the rows over, and then go bigger.

Toggles. What each toggle does is add a further set of fields, or a further step. Skip it and off makes the facebook posts scraper finishes sooner; use it and the results carry more detail. Nothing is ever enabled that you did not ask for.

Storage name. Hand a run its own storage name and everything it saves stays walled off from every other run, which is worth doing when you use you use the facebook post extractor regularly and want last week's output kept clear of today's.

Region. When a region setting is offered, it determines which version of a page gets read. Should your results look thin, switching to a different region is usually the quickest fix for a facebook post downloader.

💎 Getting More From It

• Paste it in just as it is. The facebook posts scraper takes whatever you hand over and explains anything it cannot work with, so tidying your list beforehand is not something you need to do.
• Re-run rather than retry by hand. If a source was briefly unavailable, running the facebook data shares again is usually enough.
• Work in smaller batches. A handful of modest runs is far easier to review than one giant one, and every run holds on to its own dataset.
• Compare across time. Put the same facebook posts scraper on a schedule and it will show you what changed, something one export on its own can never do.
• Export sooner rather than later. Rows are saved as they arrive, so the export from a facebook post extractor run can be exported before it has finished.
• Open narrow, then broaden. A brief run proves the facebook posts scraper is set up exactly as you want.
• Give storage a name. Assign each run a storage name of its own, and its files will never mix with another run's.
• Set it on a timer. Let it go automatically, and each pass adds a new dataset with the time it was taken.
• Keep an eye on the log. The facebook posts scraper reports each thing it is doing, so even a slow run can be seen making progress.
• Give each run a maximum cost whenever a large job needs a firm ceiling.

Feeding the facebook data shares output into a spreadsheet or a database is the usual next step, and the column names stay stable between runs so a saved import keeps working.

📶 Bigger Jobs

The facebook posts scraper was designed for repeat use rather than a single outing. Rows appear while the run is still going, so a big job is useful to you before it ends, and a job that stops early is never a write-off.

1. Begin with a tiny run. Two or three are plenty to prove items confirm the facebook posts scraper is configured just as you meant.
2. Cap the spend. Attach a maximum cost to each run and a sizeable job holds no surprises.
3. Put it on a schedule. Every scheduled run leaves its own dataset behind, so your history grows on its own.
4. Collect by API. Pull each dataset straight into your own system from the facebook post export tool output.
5. Keep an eye on the log. Progress keeps updating throughout, so a lengthy run never leaves you wondering whether it has stalled.

You are only charged for what the facebook posts scraper actually returns, so a run that turns up nothing costs you nothing. That makes it perfectly safe to aim at a wide list and let it work out what really exists.

💷 What It Costs

Every row starts with a post_type field naming exactly what it is, so a mixed timeline never arrives as one undifferentiated pile:

• Reel — a short vertical video posted to Reels
• Video — an ordinary video post
• Image — a single photo
• Carousel — one post holding several photos
• Shared — this profile resharing another profile's post. The row also names the original author and links to the original post
• Text — a post with no photo or video

The same names drive the kind filter, so a run can be narrowed to one of them.

Being straight about the limits. These are not missing features — the source does not publish them, and a column that is always empty is worse than no column:

Applies to	Not available	Why
Photo, carousel and text posts	View count	Facebook does not publish a view count for anything that is not a video. Nothing returns one, so none is invented here.
Every kind	Who reacted, by name	Only the totals per reaction are public.
Reels and videos opened by their own link	Per-reaction breakdown	A single reel or video page returns only its total. Scraping the same reel from its profile timeline returns the full breakdown, so prefer a username or page over a one-off link.

🧺 Keeping Your Results Tidy

Every run of the facebook posts scraper puts its results in a separate dataset, so one run never wipes out another. Keep to a handful of habits and the runs can accumulate without becoming a nuisance.

• Give each run a storage name that says what it covered, so a facebook post export tool archive stays readable.
• Send it directly to CSV or Excel if someone will be reading it.
• Pull JSON through the API when a program will read it, which is the usual facebook data shares setup.
• Hold on to the source field. It is what allows a row to be verified months down the line.
• Put a date on your exports. The facebook posts scraper captures what was public at that moment, and public data keeps moving.

When the job comes round regularly, setting a spreadsheet or the database at the facebook post extractor output up once and letting it refresh itself usually beats exporting by hand.

🔎 A Real Example

Rows from the facebook posts scraper hands over turn up in the order they were found. Load them into a spreadsheet and the layout is plain: a line per item, a column per field, ready to sort or filter without any cleanup beforehand.

• Stable columns. The same fields appear on every run, so a saved import or a facebook post export tool pipeline keeps working.
• Every row is checkable. The address a row came from travels alongside it, so if a result looks odd you can open it and confirm it yourself.
• Honest gaps. Where Facebook has published nothing, you get an empty field. The facebook posts scraper never makes up a value to give a row the look of completeness.
• Repeats are merged. Entries that show up more than once are folded together, so listing the same item twice will not cost you twice.

That combination is what makes the facebook posts scraper usable as a data source rather than a one-off export. A facebook data shares whose columns move between runs cannot be automated against.

🚧 What It Will Not Do

• Whatever the facebook posts scraper hands back was already published in public before it got there. No private material, no pages sitting behind a login, no account required of you.
• What comes back reflects what a source has actually made public. Where a source is sparse or newly created, you will see fewer rows, and you are told as much rather than having the list padded out.
• Missing values are never guessed at by the facebook posts scraper. An empty field simply means the platform published nothing there.
• Nothing protected is worked around, and you only ever receive what any visitor who is not signed in could view.
• How you put the results to work is your call and your responsibility: GDPR, CAN-SPAM, CCPA, PECR and whichever local rules cover your situation all still apply.

🩹 Messy Input

Plenty of tools throw away an entire run because one entry was bad. The facebook posts scraper takes a gentler approach: your entries are all checked before any collecting begins, and anything it cannot use gets its own line in the report, telling you the reason, what that box will accept, and what it will not.

The entry you pasted	How it gets handled
A link that belongs to some other site	You are told which site it points to; that one is left out and the rest go ahead
Plain wording typed into a link box	You are told a link is needed, with an example to follow
An empty line	Passed over without fuss, and noted in the summary
Nothing at all worth keeping	You are given the reason, and the run still ends successfully rather than in red

That behaviour is why is why a facebook post extractor run is safe to put on a schedule. A single dead link among two hundred costs you that one link, never the whole run, and the facebook posts scraper always names the entry involved.

If the source changes shape mid-run, or the connection cuts out, the facebook posts scraper comes to a halt with a short message, keeps every row it has saved so far, and finishes as a successful run all the same. Anything that crashes outright loses the rows you paid for, and facebook post downloader is built not to do that.

🔧 If Something Goes Wrong

The same few causes are behind most problems. Whichever one it is, the facebook posts scraper spells it out in the log, and the remedies are below.

Your run completed with an empty result. In most cases the input you gave pointed somewhere private, or somewhere that has since disappeared. The facebook posts scraper lists every skipped entry alongside the reason, so your log names the culprit for you. Try opening the address while signed out of the site: if it is not visible to you, it is not visible to neither can a facebook post extractor.

You expected more rows than you received. Look at the limit in your settings first — that is normally the answer. Raise it, rerun, and if the total still falls short, the source simply does not publish as much as you thought; and the facebook posts scraper shows what genuinely exists instead of inflating the count.

Some of your entries were passed over. Consider it is the facebook posts scraper protecting your run. Each entry that was passed over appears in the report with the fault and with what that box expects. Put those right and send just them through again, since a facebook post downloader run is inexpensive while the list stays short.

Your run ended sooner than planned. Either a spending ceiling was reached or the source became unavailable. Both are reported in plain language, and everything collected first is already saved. Running the facebook post export tool again usually completes it.

This week's results differ from last week's. Public data changes. The facebook posts scraper records what is published at the moment it runs, which is exactly why running a facebook data shares on a schedule is more useful than a single export.

🤔 Questions People Ask

Does the Facebook Posts Scraper need a Facebook login or password?

No. Pages that are already public are all the facebook posts scraper ever reads, so there is no account or password to supply and you will never be asked for one.

How big a list can results can the facebook posts scraper return?

However many the source has made public. If you would rather a run wrapped up sooner, or you want the spend to stay predictable, put a cap in the limit settings.

What if the link you paste is the wrong sort?

You are told which entry was at fault and what that box will accept, and the facebook posts scraper skips that one alone. Everything else keeps going, and the run still finishes successfully.

Can the export the facebook posts scraper results go into Excel or CSV?

Yes. Each run builds up a dataset, and from there the results come out as CSV, Excel, JSON or XML, or straight through the API.

What if a run comes to a halt midway?

Whatever had been collected by then is already safe. Because the facebook posts scraper saves each row the moment it appears, a run that stops early still leaves you with data you can use, plus a message telling you what went on.

Is there a way to run the facebook posts scraper automatically?

Yes. Set a schedule and every run leaves behind a dataset of its own, so a history builds up for you with no further effort.

Does the data from the facebook posts scraper give accurate data?

What you receive mirrors whatever Facebook had on display the moment the run took place. Nothing gets made up on your behalf; where a field is not published, you get a blank back instead of an estimate.

🔤 Plain-Word Glossary

Term	How we use it here
Run	One execution of the facebook posts scraper, with its own dataset and log.
Dataset	Where the results collect as a table, ready to take away as a file or pull in through the API.
Row	A single item, with everything known about it kept on one line.
Field	Any single column making up a row, a title or an address for instance.
Storage	Files that come down during a run are held here, on an account belonging to you.
Storage name	A label you choose so one facebook post extractor run's files stay separate.
Limit	The point at which a run stops taking on more, so both time and cost stay in hand.
Schedule	A timer that runs the facebook post downloader for you and keeps each result.

None of these are specific to this actor — they are the same words the platform uses everywhere, so anything you learn here applies to the next facebook post export tool you run too.

🛡️ Your Data

• Reading public pages and writing rows into your dataset is all the facebook posts scraper does. Nothing more.
• The list you paste serves that one run only, and nothing is retained afterwards.
• Downloads sit in storage that belongs to your account alone, reached by links with no sign-in details attached.
• No account, password or personal login is ever requested by the facebook data shares.
• Ownership of the results sits with you: take them elsewhere, wipe them, or leave them where they are indefinitely.

Your input, then public pages, then your dataset — that is where the data goes with path for the facebook posts scraper, and nowhere further. Any facebook post extractor that came looking for your account credentials would be acting well beyond anything this one does.

🧷 Related Tools

If the facebook posts scraper has earned its place for you, the ones below handle neighbouring jobs. Each is built around its own source instead of stretching to cover everything poorly.

• Facebook Albums Scraper — Facebook data, exported the same way.
• Facebook Comments Scraper — Facebook data, exported the same way.
• Facebook Events Scraper — Facebook data, exported the same way.
• Facebook Followers and Following Scraper — Facebook data, exported the same way.
• Facebook Page SEO Scraper — Facebook data, exported the same way.
• Facebook Page Transparency Scraper — Facebook data, exported the same way.
• Facebook Pages Profile Scraper — Facebook data, exported the same way.
• Facebook Photos Scraper — Facebook data, exported the same way.
• Facebook Post Engagement Scraper — Facebook data, exported the same way.
• Facebook Reactions Scraper — Facebook data, exported the same way.
• Facebook Reels Scraper — Facebook data, exported the same way.
• Facebook Reviews Scraper — Facebook data, exported the same way.

Browse everything at apify.com/premiumscraper.

✉️ Get in Touch

Questions about the facebook posts scraper, a bug, or a filter you would like added? Email premiumscraper@gmail.com and you will get a reply.

Where the facebook posts scraper did not give you what you expected, pass along the run ID, since that alone is usually enough to work out what happened.

Feature requests are welcome. You can reach the team at premiumscraper@gmail.com for anything at all — a question before you buy, or a source you would like covered next.