Share buttons that load fast, look like your site, and count what people actually share.
The complete list — what each part does and what it is there for.
X, Facebook, WhatsApp, LinkedIn, Pinterest, Reddit, Telegram, Bluesky, Threads, Mastodon, Tumblr and email, plus copy link, print and the phone's own share sheet. No dead networks padding the list.
Mark the one sentence in an article worth repeating and a reader can post it in a single click, with a link back to you.
Solid, outline, soft, minimal, pill or square — with rounded, circular or square corners, three sizes, and labels that can hide themselves on a phone where a labelled row would wrap into a wall.
Each network in its own brand colour, everything in one neutral, or everything in a colour you pick. The buttons inherit your theme's typography either way, so they read as part of the page.
Above the content, below it, floating alongside it, or pinned to the bottom of the screen on a phone. Use as many as suit the page — and a shortcode for anywhere else.
Choose which content types get buttons, whether archives and the front page do, and switch them off for one particular post from the editor without keeping a list of exceptions.
Tick the kinds of content that carry buttons, and the archives if you want them — both lists built from your own site, custom post types included. Nothing asks for an ID, and nothing is offered that buttons could never appear on.
"But never on these" takes a page, a post, a product or a whole category — picked by name — and a category covers everything filed under it. Individual posts can still be switched off from the editor.
Limit it to desktop, tablet or mobile — decided by the width of the window, so it survives page caching — to signed-in or signed-out visitors, or to particular roles. Give it a window of dates, days of the week and hours if it is only meant to run for a while.
Presses are counted on your own site, per post and per network. Nothing about the reader is stored — a post id and a network name is the whole row.
No jQuery, no network SDKs, no tracking pixels, no external fonts. One small stylesheet and one small script, both loaded only on pages that show buttons, and only after the page itself.
Every network button is a plain link that works with scripts disabled. The script only adds the things a link cannot do — copying, printing and the device share sheet.
Real buttons and real links, each with an accessible name, visible focus rings, and motion that respects a reduced-motion preference.
Every screen in the plugin arrives without a page load, and every save happens where you are standing. WordPress fetches the whole of wp-admin's CSS and JavaScript again to change one panel; this fetches the panel. The screen you are on is still there while the next one is on its way, and the one you are heading for is usually already in hand — a pointer takes a moment to reach a menu item, and that moment is spent fetching.
A save answers in the corner of the screen, bordered in the colour of what it is telling you and saying what was saved rather than just "Saved". Four seconds, and hovering holds it open. No reload, and no scrolling back to find a notice above the header three hundred pixels from the button you just pressed.
A WordPress admin request spends about a second in its own bootstrap before a plugin gets a word in, and fetching when your pointer arrives only buys back a fraction of it. So the plugin's other screens are fetched quietly while you read the first one — one at a time, only while the browser is idle, and never on a metered connection. By the time you click a tab the answer has been in memory for seconds.