Publishing a post and then manually resharing it to six social networks is a habit worth breaking — both for the time it burns and the inconsistency it produces. FS Poster automates the whole distribution layer from inside WordPress: auto-publish on post publish, schedule to a visual calendar planner, and share to Facebook, Instagram, X/Twitter, LinkedIn, TikTok, YouTube (including Shorts), Threads, BlueSky, Telegram, Discord, Reddit, Pinterest, and a couple dozen more networks — per-network message customization included.
The 8.x line has been a feature surge — watermarks, YouTube Shorts, content ideas, workflow notifications — paired with a serious internal rebuild (new routing, dependency injection, and request validation layers in the latest releases). Here’s the working review at 8.0.2.
Competitive Features
- Twenty-plus networks under one schedule. From the majors (Facebook, Instagram, X, LinkedIn, TikTok) to the long tail (Threads, BlueSky, Mastodon, Truth Social, Odnoklassniki, Plurk, Xing, Blogger) — one planner covers the entire distribution map.
- Watermark and text templates. Add logos or custom text to images before sharing (8.0.1), with template reuse — brand-consistent social images without a design step.
- YouTube Shorts publishing. Full Shorts integration with post sharing, first comments, and insights — the vertical-video channel handled like any other network.
- Workflows with notification actions. Automation rules with a Telegram notification action, log details, and retry — post-publish processes, not just post-publish shares.
- Content Ideas module. Save and manage content ideas without scheduling dates — the planning half of social media that most auto-posters skip entirely.
- AI message generation. OpenAI configuration for post text — per-network captions generated rather than typed.
- Multi-account filtering. Publications filterable by post categories, with account sharing across users — agencies can pool accounts under permission.
- Insights collection. Published-post metrics (likes, comments, shares) collected back into the plugin — distribution and measurement in one place.
Key Features
- Auto-share on publish with delay control. Posts share automatically after creation, on a configurable timer — including background sharing without opening the editor.
- Visual calendar planner. Bulk scheduling across accounts and networks, with the “specific posts” selection syncing correctly when bulk schedules are reopened (8.1.2 fix).
- First-comment strategy. X/Twitter and YouTube first comments (auto-replies) with link cards — the engagement tactic done as a feature, with 8.1.x fixing the duplicate-post-on-retry bug when a space-only first comment failed.
- Per-network message templates. Custom text per social network with tags and
{short_link}variables, Twitter length limiting to prevent API errors. - Media handling. Video sharing via FFmpeg (with a hardened Process wrapper replacing exec calls in 8.1.1), Instagram segment-splitting for long videos with audio preserved, proxy support for all networks.
- URL shorteners. Bitly, TinyURL, and integrated shortener support for tracked links.
- Hardened internals. 8.1.2 rebuilt the plugin’s routing, dependency injection, and request validation layers; REST API endpoints now require an activated license; FFmpeg path handling got input sanitization (8.0.2).
- Webhooks. Outbound webhooks connect post-publishing events to external systems.
Comparison with Competitors
FS Poster vs Revive Old Posts
Both live in the WordPress distribution layer, but they answer different jobs: new-post amplification versus archive resurfacing.
| Aspect | FS Poster | Revive Old Posts |
|---|---|---|
| Core job | Publish and schedule new posts | Re-share older content on rotation |
| Scheduling | Calendar planner, per-network | Interval-based recycling |
| Networks | 20+ including Shorts, Threads | Major networks |
| Media features | Watermarks, video, Shorts | Images |
| Ideas/Workflows | Built-in | No |
They actually stack: FS Poster handles the publish moment, a recycling plugin keeps the archive alive on rotation — complementary halves of a distribution strategy.
FS Poster vs AAWP (content layer comparison)
An odd-looking pairing until you see both as “content out” systems: FS Poster distributes your content outward, while the Amazon affiliate plugin pulls marketplace content in.
| Aspect | FS Poster | AAWP |
|---|---|---|
| Direction | WordPress → social networks | Amazon → WordPress |
| Content type | Your posts | Product boxes and lists |
| API dependency | Per-network credentials | Amazon PA-API/Creators API |
| Overlap | None | None |
For an affiliate site, both layers belong: AAWP builds the product content, FS Poster distributes the articles that contain it.
Recommended Stack: Social distribution converts best when the destination pages are fast — pairing FS Poster with a performance optimizer keeps the shared links landing on quick-loading pages, protecting the click-through you paid for in posting effort.
Official Changelog
The registry tracks one version line for this plugin; the changelog below covers the current registry version.
Version 8.0.2
Release Date: June 10, 2026
- Improved input sanitization for FFmpeg path handling
- Enhanced overall security and stability of the plugin
Frequently Asked Questions
Which social networks does FS Poster support?
Over twenty: Facebook, Instagram, X/Twitter, LinkedIn, TikTok, YouTube (community posts and Shorts), Threads, BlueSky, Mastodon, Pinterest, Reddit, Telegram, Discord, Tumblr, Medium, Google Business Profile, VK, Odnoklassniki, Xing, Plurk, Blogger, Flickr, and Truth Social — each connecting with its own credentials.
Is the GPL version the full Pro plugin?
Yes. The GPL build is the complete plugin source under its original license with all networks, planner, workflows, and watermark features enabled. The vendor’s license key for auto-updates is what’s absent.
Can I use it on multiple sites?
The GPL license permits unlimited installations across personal and client sites with no per-domain activation — each site connects its own social accounts.
Do I need FFmpeg on the server?
For video sharing, yes — FFmpeg processes video uploads (including Instagram segment-splitting). The vendor documents installation, and 8.1.1 hardened how the plugin invokes it (a safer Process wrapper instead of raw exec calls).
Does it support scheduled and automated posting?
Both: auto-share on publish with a configurable delay, calendar-based scheduling via the Planner, and Workflows for post-publish automations with Telegram notifications, logging, and retry.
Can multiple team members share accounts?
Yes — an account owner can make accounts public for other users to publish through, and publications filter by post categories. Agencies typically structure this as pooled client accounts with per-user access.
Leave a Reply