Social Sharing Buttons on WordPress in 2026: Jetpack’s Fixed List and Your Alternatives

If you’re still hunting for the “add a custom service” option in Jetpack’s Sharing settings so you can bolt on a VKontakte button, stop looking. It’s gone, and it isn’t coming back the way it used to work. Jetpack’s Sharing Buttons module now ships with a fixed, predefined list of services, and there’s no field left to type in a custom one.

This covers what’s actually in that list today, why the custom option disappeared, and how to add VK.com (or anything else Jetpack won’t do) with a dedicated sharing plugin instead.

Why the custom service field disappeared

Jetpack’s Sharing module used to let you define a custom button by supplying a name, an icon and a URL pattern using variables like %post_url% and %post_title%. That’s how older guides (including our own, now retired) walked people through wiring up VKontakte, since Jetpack never added it as a native option.

Automattic has since rebuilt the sharing settings around a curated, block-editor-friendly list rather than an open-ended custom builder. The settings screen at Jetpack, Settings, Sharing (or the Sharing Buttons block if you’re on a block theme) now only lets you toggle services on or off and pick a button style. There’s no text field for a custom name, icon or link left in the interface.

If you’re on an older Jetpack version where a custom field still technically renders, treat it as legacy: it isn’t documented, isn’t supported, and can break silently on the next update.

What’s actually in Jetpack’s list right now

As of this Jetpack release, the predefined sharing services are:

Notably absent: VKontakte, WeChat, Line, Xing, Telegram Instant View, and anything regional Jetpack hasn’t chosen to prioritise. If your audience actually uses one of those, you need a different plugin, not a workaround.

Getting VK.com (or anything else) back with a dedicated plugin

Two plugins consistently do this well and stay maintained:

• AddToAny Share Buttons (300,000+ active installs, updated regularly): a lightweight universal share button plus a configurable row of individual icons, including a VK button, from a library of 100+ services. Good if you want minimal setup and a “more” fallback for everything else.
• Sassy Social Share (100,000+ active installs): explicit VKontakte support with share counts, plus floating and inline placement options and per-service icon styling. Good if you want more visual control than AddToAny offers.

Setup steps

If you only need VK and nothing else Jetpack is missing, a single-purpose plugin like VKontakte Share Button is lighter weight than pulling in a full sharing suite, but check its last-updated date before installing anything single-purpose: small plugins get abandoned more often than the major suites above.

Running Jetpack and a sharing plugin together

You don’t have to give up Jetpack’s other features to fix this. Sharing is a separate module from things like Stats, Protect or Backup, and you can disable just that one module in Jetpack’s dashboard without affecting anything else. There’s no supported way to run two sharing button sets on the same post without visual duplication, so pick one source of truth.

Frequently asked questions

Can I still add a custom sharing service to Jetpack at all?

Not through the settings screen. The custom name/icon/URL field has been removed from current Jetpack versions. Developers can still hook into sharing output with code (Jetpack exposes filters for this), but that’s a theme/functions.php job, not a settings toggle.

Why was VKontakte never added natively?

Jetpack prioritises services with broad, mainstream usage across its install base. VK’s audience is concentrated in specific regions, so it’s never made the cut, even as newer networks like Bluesky and Threads have been added.

Will switching plugins break my existing share counts?

Jetpack’s sharing buttons don’t display share counts by default, so there’s nothing to carry over. If you’re moving from another counting plugin, most share-count APIs (Facebook’s especially) have been deprecated for years, so don’t expect accurate historical counts from any plugin.