To export Facebook Page posts, paste the Page link into the Facebook Posts Exporter and download one row per post, with the post type, caption, likes, comments, shares, video views, date and hashtags, as a CSV, Excel or JSON file. It works on any public Page, including Pages you do not manage, with no developer app and no access token.
This guide covers what the file contains, how far back a run reaches, the jobs a post list is good for, where Meta's own export routes stop, and how to go from a list of posts to the comments underneath them.
What a Page export gives you that scrolling doesn't
Facebook shows a Page as a feed: one post at a time, numbers half-hidden behind hover cards, Reels on a separate tab. That is fine for reading and useless for comparing. You cannot sort a feed by shares, you cannot see at a glance that a Page posted eleven Reels and two photos last month, and you cannot hand a feed to a client.
A post export turns the feed into a table. Every post becomes a row, every metric becomes a column, and the questions that took an afternoon of scrolling become a sort or a pivot table:
- Which posts drew the most shares this quarter?
- Do Reels outperform photo albums on this Page, or is that just our impression?
- How often does the competitor post, and on which days?
- Which posts have a thread big enough to be worth reading in full?
Step by step: from Page link to spreadsheet
- Copy the Page address. Any of these forms is accepted:
facebook.com/pagename,m.facebook.com/pagename,facebook.com/profile.php?id=…,facebook.com/people/Name/123…, or simply the Page name on its own (with or without an @). A single post link is rejected on purpose; that belongs in the comment exporter. - Paste it into the Facebook Posts Exporter.
- Leave the dates blank, or set a window. Blank dates return the Page's newest posts. The date range is available after a one-time payment and keeps only posts published between the two days, inclusive of the end day.
- Click Export posts. The result opens at its own URL, so you can refresh it, bookmark it or send it to a colleague. Results are kept for 30 days.
- Download CSV, Excel or JSON. CSV suits Google Sheets and BI tools, Excel opens without an import step, and JSON is the cleanest input for a script or an AI assistant.
The latest 5 posts of any public Page download with no signup, up to three Page exports a day. Longer history, date ranges and the media columns come with a one-time payment, never a subscription; the options are on the pricing page.
Reading the fourteen columns
The file has the same header every time, so a template or formula you build once keeps working:
- Post URL, the permanent link to the post or Reel. This is the value you paste into the comment exporter later.
- Thumbnail, the cover image of a video or the first photo.
- Type, one of Reel, Video, Photo, Album or Text. A post counts as an Album when it carries more than one attachment, and as a Reel when its link is a Reel link.
- Description, the full caption.
- Views, video plays. Facebook only publishes this for Reels and videos, so photo, album and text rows always read 0.
- Likes, Comments and Shares, the counts shown on the post when it was read.
- Posted At (UTC), an ISO timestamp in UTC. Convert to your own time zone before you chart posting hours.
- Hashtags, space-separated, and Post ID, Facebook's numeric identifier.
- Media Count, Media URL and Alt Text, filled on paid exports: how many photos are in an album, direct links to every photo or video file, and the accessibility caption Facebook attaches to photos.
The file does not include the Page's follower count, because Facebook does not return it alongside the posts. If you want engagement rates, add a follower figure by hand from the Page's About section.
How far back one run reaches
It is worth being precise here, because "export all posts" means different things on different platforms. Facebook serves a Page's timeline a few posts at a time, and each page of results takes over a second to arrive. To keep every export inside a single browser request, a run walks the Page newest first for about 75 seconds and then stops. In practice that reaches roughly the latest 120 posts.
Two consequences follow:
- For most Pages, 120 posts is months of history. A brand posting four times a week is covered for about seven months in one run, enough for a quarterly report or a launch comparison.
- A date range filters; it does not jump. The run still begins at the newest post and stops when it passes your start date or runs out of time. A window from two years ago on a Page that posts daily will come back short or empty. For a deep archive of a very busy Page, contact us rather than running the tool repeatedly.
A quick completeness check: look at the oldest Posted At value in the file. If it is later than the start date you asked for, the run reached its time limit before getting there, and the file covers only the newer part of your window.
Five jobs a post list does well
Benchmarking a competitor Page
Export your Page and two or three rivals for the same period. Put them side by side and compare posting frequency, format mix (the Type column) and median shares per post. Medians matter: one viral Reel can make a Page's average meaningless.
Auditing which formats work
A pivot table with Type as rows and average Likes, Comments and Shares as values answers the Reels-versus-photos question with your own Page's numbers rather than an industry survey. Add Posted At converted to weekday for a posting-schedule view; our best time to post on Facebook guide explains how to read it.
Monthly reporting for Pages you don't admin
Agencies often report on Pages they monitor but do not manage: a client's distributor, a sponsor, a market leader. Meta's dashboards will not show those. A date-range export of the month gives you a table to paste into the report, with post links the client can click.
Finding the posts worth mining
Sort by Comments, descending. The top rows are where the Page's audience actually talked, and those threads hold the questions, complaints and purchase intent that likes never show. That list is the shortlist for the comment export described below.
Archiving before a Page changes
Pages get renamed, rebranded, merged or deleted, and campaign posts are often removed when a promotion ends. Researchers, journalists and compliance teams export a Page's post list, captions and links included, so there is a dated record of what was published.
Meta's own export routes and where they stop
Meta offers three official ways to get post data out of Facebook. Each is the right answer in some cases, and it helps to know which:
- Meta Business Suite insights. If you manage the Page, the content section of Meta Business Suite insights shows per-post reach and engagement and can export it. It includes reach and impressions, which no outside tool can see. It only covers Pages you have a role on.
- Download Your Information. Facebook's download a copy of your information tool packages your own account's posts, photos and activity. It is the right tool for a personal backup and does not reach anyone else's Page.
- The Graph API. The Page feed endpoint returns posts with a Page access token. Reading Pages you do not manage requires the Page Public Content Access feature and App Review, and Meta documents a ceiling of roughly 600 ranked posts per year per Page. For a developer building on Pages they own, it is the proper route.
Academic and non-profit researchers studying public content at scale can also apply for Meta's Content Library API. For everyone else who needs a public Page's post list without admin rights or a developer app, a hosted exporter is the practical option.
From the post list to the comments underneath
The post file tells you where the conversation is. The comments tell you what it says. The two-step workflow most of our users settle into:
- Export the Page's posts and sort by the Comments column.
- Copy the Post URLs of the top threads.
- Paste one into the Facebook comment exporter to download every comment with author, text, likes, replies, date and reply links, or paste several at once as described in our guide to bulk exporting Facebook comments from multiple posts.
One thing to expect: the Comments number in the post file is Facebook's lifetime badge count, which includes deleted, hidden and spam-filtered comments. On large posts the comment file usually holds noticeably fewer rows than the badge. That gap is Facebook's moderation, not missing data.
Notes from the first 78 Page exports
The Facebook Posts Exporter went live on 28 October 2026, and this guide is written from running it. In its first three days visitors ran 78 Page exports across 26 different Pages, 390 posts in total. Reading those rows shaped several points above:
- Reels are the most common format, but not by much. Of the 390 posts, 129 were Reels, 123 photos, 47 videos, 47 text posts and 44 albums. Pages are still mixing formats, which is exactly why the Type column is the first thing worth pivoting on.
- Views only exist on video. 106 of the 129 Reels and 22 of the 47 videos carried a view count; no photo or text post did. Comparing a photo's zero views against a Reel's 60,000 is meaningless, so compare across formats on shares and comments.
- Every photo had alt text. All 123 photos and all 44 albums carried an accessibility caption, almost always Facebook's automatic description. It is a cheap way to see what a Page's images actually show without opening them.
- Hashtags are a Reels habit. About 70% of Reels used at least one hashtag against about 43% of photos.
- The time-bounded walk is deliberate. We measured roughly 120 posts per run before choosing to keep exports synchronous. A result in about a minute, at its own link, proved more useful in testing than a deeper export that leaves you waiting on a background job.
The column names, the 5-post no-signup limit, the three exports a day and the run length are the live product values at the time of writing. Facebook's rules on what Pages may publish are in Meta's Community Standards.
Handling another Page's data with care
A post list is mostly Page content, not personal data, but captions can name or tag people, and a comment export built on top of it certainly will. Use the file to measure and learn: quote numbers rather than copying captions wholesale into your own content, keep competitor files internal, and delete exports you no longer need. If any of it concerns people in the EU, the GDPR's principles of purpose limitation and data minimisation are a sound default even where they do not strictly apply.
Export a Facebook Page's posts →
Related reading: bulk exporting Facebook comments from multiple posts, Facebook Page comments for brand monitoring, the best time to post on Facebook.