Facebook Feed – WordPress Facebook Plugin is a commercial plugin from Elfsight that pulls content from a public Facebook page and renders it inside a WordPress site as a styled, filterable feed. It suits site owners who want page posts, photos, albums and videos to appear on their own domain without sending visitors to Facebook, and it is aimed at users who prefer configuration screens over custom code. The item has sold 2,514 copies on CodeCanyon and holds a 4.67 out of 5 rating across 85 reviews, which places it among the better-established Facebook Feed Social Networking extensions in that marketplace.
Elfsight is the developer behind the plugin, and the company has built a catalogue of embeddable widgets rather than a single product, which shows in how the settings are organised.
What the plugin actually does once it is installed
The core job is straightforward: connect a Facebook source, choose what to show, and place the result on a page. The interesting part is how much control the settings expose over that output.
Content types are handled individually. Posts, photos, albums and videos each have their own tab in the widget, and any tab can be switched off. A site that only ever publishes photo albums can hide the rest of the menu entirely, which keeps the interface clean instead of offering visitors filters that lead nowhere. Albums get their own detail screen showing the album name, description, photo count, last update time and the images themselves.
Each post is rendered with its full set of metadata: author, publication date, formatted message text with working links and tags, image, reaction breakdown, comment count and share count. Which of those elements appear is a per-widget decision, so a minimal design and a data-dense one are both achievable from the same settings panel.
Photos and videos open in a popup rather than navigating away. That popup carries the media, its author, description, publication date, reactions, comment count and the comments themselves, with arrow navigation to move between items. New comments load as they arrive, and a Load More button pulls the full comment thread. Sharing is available directly from the popup to Facebook and other networks.
The header area mirrors the connected page: cover image, profile picture, page name, like count and the verified badge where Facebook supplies one. Every element can be hidden, and the whole header can be disabled. Custom action buttons — like the page, share the page, contact — can be attached to the header, which turns a passive feed into a small conversion surface.
Sizing is handled in two modes. The widget can stretch to fit its container, or it can be given a fixed height with internal scrolling. Content is responsive and adapts to mobile screens, and the plugin is marked as Gutenberg-optimised and compatible with Elementor, Layers WP and Cornerstone, so it can be dropped into a page builder layout rather than hand-coded into a template.
Where this fits, and where it does not
The strongest fit is a business, band, restaurant or nonprofit that treats its Facebook page as the primary publishing channel and wants that activity visible on the website without duplicating every post manually. The plugin keeps the site looking current even when nobody has logged into WordPress for a fortnight, because the content is pulled from Facebook rather than stored locally.
A second good fit is an agency building a site for a client who already understands Facebook’s composer but not WordPress. Handing over a site where updates happen in a familiar interface removes a training burden and a recurring support request.
Media-heavy pages benefit too. Photographers and event organisers who upload albums to Facebook can surface those albums as a browsable gallery on the site, with the popup viewer handling the lightbox work that would otherwise need a separate gallery plugin.
It is the wrong choice in a few situations. If the Facebook page is private, or the content lives on a personal profile rather than a page, the plugin has nothing to connect to — it works with public pages. Sites in regulated industries that need a full editorial audit trail before anything appears publicly should not use it either, because content goes live on the website the moment it goes live on Facebook, with no review step in between. And anyone who needs the feed indexed as first-party content for search should look elsewhere: the posts are rendered client-side from Facebook’s data, so the text is not part of the page’s own markup in the way a native WordPress post would be.
Strengths and limitations
Strengths
- Genuinely granular display controls — individual post metadata fields, header elements, content tabs and menu visibility can all be toggled independently.
- Popup viewer for photos and videos keeps visitors on-site and includes comment loading and cross-network sharing in the same overlay.
- Two sizing modes (fluid and fixed-height with scroll) cover both full-width hero placements and narrow sidebar widgets.
- Page-builder friendly, with declared compatibility for Elementor, Layers WP and Cornerstone, plus Gutenberg optimisation.
- Source files are included (JavaScript, HTML, CSS, PHP), so a developer can inspect or extend the front-end output.
- Localisation has been actively expanded — Japanese, Bulgarian, Slovak, Ukrainian, Estonian, Icelandic, Taiwanese Mandarin and Hebrew were added across 2019 and 2020 releases.
Limitations
- The last vendor update recorded is October 2020, version 1.15.0, which addressed Facebook API v8.0 support. Facebook has moved through many API versions since, and the listing does not state which current version is supported. Buyers should verify the plugin still authenticates and returns data before committing, because API deprecation is the single most common way a plugin of this type stops working.
- Support for Events is restricted to managed pages only, and the plugin requires a different authorisation type depending on whether the source is a managed page or a public page. That distinction is easy to miss during setup.
- Because the feed is fetched at runtime from Facebook, it depends on Facebook’s availability and rate limits. An outage or throttling on their side shows up as an empty or partial widget on the site.
- There is no moderation layer. Anything posted to the connected page appears on the website automatically, including replies and system messages, unless the relevant content type is disabled.
- Compatibility is declared up to WordPress 5.7.x. Sites on newer major WordPress releases are outside the stated support range.
How it compares with the wider category
Facebook feed tools for WordPress generally fall into three groups: free plugins that embed Facebook’s own page plugin, lightweight custom-coded embeds, and paid widgets like this one.
The free route costs nothing and is maintained by Facebook itself, but the styling is largely fixed and the output looks like Facebook rather than like the host site. It also offers little control over which post elements appear. A custom-coded embed gives total control but requires a developer every time Facebook changes an endpoint, which is a recurring cost rather than a one-off one.
Paid widgets sit in the middle. They trade a licence fee for a settings interface, consistent styling that can be made to match a theme, and a vendor who absorbs API changes. Within that group, this plugin’s differentiators are the depth of the per-element display controls and the popup experience with comment loading. Competing paid options tend to emphasise layout variety — masonry, carousel, grid — more than metadata control, so the choice often comes down to whether the priority is how the feed looks or how much of each post is shown.
The trade-off with any paid widget is dependency. The buyer is relying on the vendor to keep pace with Facebook’s API, and the update history here shows that work was happening consistently through 2020 but the listing gives no information beyond that point.
Frequently Asked Questions
Does this plugin work with a personal Facebook profile?
No. It connects to public Facebook pages and, for Events, to managed pages. Personal profiles are not a supported source, which is a deliberate restriction tied to how Facebook’s API exposes data rather than a missing feature. Anyone whose content lives on a personal profile would need to convert it to a page first.
Will the Facebook feed slow down my WordPress site?
The plugin loads content from Facebook at runtime rather than storing it in the WordPress database, so the initial page render is not blocked by a large local query. The trade-off is a dependency on Facebook’s response time. Sites with heavy traffic or strict performance budgets should test the widget under load before rolling it out site-wide.
Can the plugin display Facebook photos and videos in a gallery?
Yes. Photos, albums and videos are supported as separate content types, and albums get a dedicated view showing the album name, description, photo count and last update time. Clicking any photo or video opens it in an on-site popup with arrow navigation, so visitors browse the media without leaving the website.
Is coding knowledge needed to set it up?
No coding is required for standard use. Setup involves installing the plugin, configuring the widget settings in the admin panel, and placing the resulting shortcode or block on a page or template. Source files are included for developers who want to modify the front-end output, but that is optional rather than part of the normal workflow.
Verdict
This is a well-specified plugin for a specific job: showing a public Facebook page’s posts, photos, albums and videos on a WordPress site with real control over how much of each post is displayed. The 2,514 sales and 4.67 rating suggest a product that has satisfied a substantial number of buyers, and the feature set backs that up — the per-element toggles and the popup viewer with comment loading are more thorough than most tools in this bracket.
Buy it if the site’s Facebook page is the main publishing channel, if the design needs to match the surrounding theme rather than look like an embedded Facebook box, and if the WordPress installation is on version 5.7.x or earlier. Do not buy it if the content source is a private page or personal profile, if every post needs editorial sign-off before appearing publicly, or if the site runs a recent WordPress major release and cannot tolerate an unsupported combination. Anyone in that last group should confirm current API and WordPress compatibility with the vendor before purchasing, since the listing itself does not state it.
