Jetpack

What Is Jetpack?

Jetpack is a multi-feature WordPress plugin built by Automattic, the company behind WordPress.com, that bundles a wide range of capabilities, security, performance, backups, statistics, social sharing, and more, into a single plugin connected to the WordPress.com cloud. Rather than installing separate plugins for each task, site owners can enable a broad set of features from one place, with much of the heavy lifting handled by Automattic's infrastructure.

Jetpack is one of the most widely installed WordPress plugins in the world, distributed through the WordPress.org directory with a very large active-install base. It uses a freemium model: a generous set of features is free, while advanced capabilities, real-time backups, malware scanning, advanced search, and ad-free video hosting, are sold as paid plans or as individual standalone plugins that share the Jetpack framework.

It is important to be precise about what Jetpack is. It is a WordPress plugin that runs on the server as part of a WordPress installation, and it is not a browser extension or a standalone hosted service. What makes Jetpack distinctive is that many of its features depend on a connection to the WordPress.com cloud: the plugin links the self-hosted site to Automattic's servers, which then provide services like statistics, image and asset delivery via a content delivery network, and security monitoring from outside the site.

That cloud connection is the key to understanding Jetpack. Features such as the image CDN serve media from Automattic's wp.com domains rather than from the site's own server, offloading bandwidth and speeding up delivery. Because those externally hosted assets are visible in the page's markup, Jetpack is one of the more recognizable plugins to detect from the outside, even though it is just one plugin among the many a WordPress site might run.

How Jetpack Works

Jetpack is organized as a collection of modules, each providing a distinct feature, that can be toggled on or off. When you connect Jetpack to a WordPress.com account, the plugin establishes a secure link between your self-hosted site and Automattic's cloud, and that link is what powers the features that rely on external infrastructure.

One of the most visible features is the image CDN (historically branded Photon, now part of Jetpack's site-acceleration features). When enabled, Jetpack rewrites image URLs in your content so they are served from Automattic's CDN domains, the i0.wp.com, i1.wp.com, and i2.wp.com hostnames. The CDN resizes and optimizes images on the fly and serves them from edge locations. Because these wp.com image URLs appear directly in the rendered HTML, they are one of the clearest signs Jetpack is active. Jetpack can similarly serve static CSS and JavaScript assets from c0.wp.com-style domains when asset acceleration is on.

Statistics is another core module: Jetpack records page views and visitor data and reports them through the WordPress.com dashboard, loading a small tracking script on the front end. Social features automatically share new posts to connected social accounts and add sharing buttons. Security features include downtime monitoring, brute-force protection, and, on paid plans, malware scanning and automated backups handled from the cloud. Additional modules cover related posts, subscriptions and newsletters, contact forms, lazy image loading, and more.

Over time, Automattic has also unbundled Jetpack into a family of standalone plugins, such as Jetpack Boost for performance, Jetpack Protect for security scanning, Jetpack Backup, Jetpack Social, and Jetpack Search, that each deliver one slice of functionality while sharing the same underlying connection framework. A site might therefore run the full Jetpack plugin or just one of these focused offshoots, but they share recognizable assets and the same wp.com cloud relationship.

Because Jetpack renders through WordPress and then rewrites asset URLs to Automattic's CDN and injects feature scripts, a visitor receives HTML that references i0.wp.com image URLs, Jetpack's own scripts from the plugin directory, and feature-specific markup. That combination of external asset domains, plugin asset paths, and script signatures makes Jetpack straightforward to identify.

How to Tell if a Website Uses Jetpack

Jetpack leaves several dependable fingerprints. StackOptic inspects them from the server side, and you can confirm the same signals by hand.

The wp.com image CDN. The clearest signal is images served from i0.wp.com, i1.wp.com, or i2.wp.com. When Jetpack's image acceleration is on, content images are rewritten to these domains, and seeing them in the page source is a strong Jetpack tell.

Plugin asset paths. Jetpack loads CSS and JavaScript from /wp-content/plugins/jetpack/. Requests to that directory, for modules like sharing, related posts, or stats, are a reliable indicator.

The stats tracking script. When the Statistics module is active, Jetpack loads a small tracking script and pings WordPress.com. References to Jetpack's stats script appear in the page source and the Network tab.

Module-specific markup and classes. Jetpack features emit recognizable markup, for example sharing-button containers with sharedaddy/jp- style classes, related-posts blocks, and contact-form markup, which point to specific Jetpack modules.

WordPress underneath. Because Jetpack only runs on WordPress, the usual WordPress signals, /wp-content/, /wp-includes/, and the WordPress generator tag, are also present, reinforcing the detection.

Method	What to do	What Jetpack reveals
View Source	"View Page Source" on the homepage or a post	i0.wp.com image URLs, /wp-content/plugins/jetpack/ assets, sharing/related markup
Browser DevTools	Inspect the Network tab and Elements	Requests to i0/i1/i2.wp.com, Jetpack scripts, the stats ping
curl -I	curl -I https://example.com	Server and caching headers; pair with curl -s to grep the HTML
Wappalyzer	Run the extension on the live page	Identifies "Jetpack" under WordPress plugins
BuiltWith	Look up the domain	Current and historical Jetpack usage plus the wider stack

A fast terminal check is curl -s https://example.com | grep -i "i0.wp.com", or grep -i "wp-content/plugins/jetpack" against the same HTML. If either matches, the site is very likely using Jetpack. For broader methodology, see our guides on how to tell if a website is built with WordPress and how to find out what technology a website uses.

A few practical notes help interpret these signals. The wp.com image CDN is only visible when image acceleration is enabled, so a Jetpack site that uses only statistics or security may not show i0.wp.com URLs; in that case the plugin asset path and the stats script become the primary tells. Conversely, the presence of i0.wp.com images is a very strong positive because nothing other than Jetpack's CDN uses those hostnames in this way. Because Jetpack is modular, the exact mix of signals varies with which features a site has turned on, which is why combining several clues, an external wp.com asset domain, the /wp-content/plugins/jetpack/ path, and module-specific markup, gives the most dependable result. Pulling the raw server response makes those signals easy to read without browser interference.

Key Features

• Site acceleration (image and asset CDN). Serve images and static assets from Automattic's global wp.com CDN to reduce load times and bandwidth.
• Statistics. Built-in traffic analytics reported through the WordPress.com dashboard.
• Security. Downtime monitoring and brute-force protection, with malware scanning and real-time backups on paid plans.
• Social sharing and auto-posting. Share new posts automatically and add sharing buttons to content.
• Related posts. Automatically generated related-content blocks powered by the cloud.
• Subscriptions and newsletters. Let visitors subscribe and receive new posts by email.
• Modular and standalone options. Run the full plugin or focused offshoots like Jetpack Boost, Protect, Backup, Social, and Search.

Pros and Cons

Pros

• Consolidates many common needs, security, performance, stats, social, into one connected plugin.
• The image and asset CDN offloads bandwidth and can meaningfully speed up media-heavy sites.
• Backed by Automattic's infrastructure and the WordPress.com cloud for reliability.
• Free tier covers a lot, with optional paid plans for advanced security and backups.

Cons

• Bundling many features can add overhead; running everything when you need only one module is wasteful.
• Several features require a connection to WordPress.com, which some self-hosting purists prefer to avoid.
• The most valuable security features (real-time backups, malware scanning) are paid.
• Single-purpose alternatives sometimes outperform Jetpack's equivalent module for a specific task.

Jetpack vs Alternatives

Jetpack's all-in-one approach competes with focused single-purpose plugins across several categories.

Tool	Scope	Strength	Best for
Jetpack	All-in-one (security, performance, stats, social)	One connected plugin, Automattic infrastructure	Site owners wanting many features from a single source
Wordfence	Security only	Deep firewall and malware scanning	Sites prioritizing dedicated security
WP Rocket	Performance only	Best-in-class caching and optimization	Sites focused purely on speed
Google Analytics / plugins	Analytics only	Detailed, industry-standard reporting	Teams wanting in-depth web analytics
Akismet	Spam only	Comment and form spam filtering	Sites needing focused spam protection

If a site uses focused plugins instead of Jetpack, the same detection techniques identify them; compare Jetpack with a dedicated caching plugin like LiteSpeed Cache when profiling a site's performance stack.

Use Cases

Jetpack is most useful for site owners who want a broad set of capabilities without assembling and maintaining many separate plugins. Bloggers and small businesses enable it for stats, social sharing, and basic security in one step. Media-heavy sites turn on the image CDN to speed up delivery and cut bandwidth costs.

It also suits hobbyist and personal sites that benefit from free analytics and downtime monitoring, content publishers using related posts and subscriptions to grow engagement, and site owners on managed hosting who want Automattic-backed backups and security on a paid plan. For competitive and market research, detecting Jetpack signals a WordPress site managed by an owner who favors an integrated, Automattic-centric toolset.

Consider a few typical adopters. A solo blogger might install Jetpack purely for its free stats and social auto-posting, never touching the paid tiers. A small business on shared hosting might enable the image CDN and brute-force protection to improve speed and security without hiring a developer. A growing publication might subscribe to a paid Jetpack plan for real-time backups and malware scanning, treating Jetpack as its managed safety net. The common thread is a preference for consolidation and reliance on Automattic's cloud rather than stitching together specialist plugins.

From a sales-intelligence standpoint, spotting Jetpack is a meaningful signal. It indicates a WordPress site, narrowing the platform immediately, and suggests an owner who values an all-in-one, cloud-connected approach, often a smaller team or solo operator rather than an enterprise with a dedicated stack. That profile is useful context when qualifying prospects, and identifying it automatically across many domains is exactly what a technology-detection scan delivers, complementing the lead-qualification ideas in what is technographics, using tech-stack data to qualify leads.

Frequently Asked Questions

Is Jetpack free?

Jetpack offers a substantial free tier, distributed through WordPress.org, that includes statistics, social sharing, basic security, downtime monitoring, and site-acceleration features. Advanced capabilities, real-time backups, malware scanning, advanced search, and ad-free video, are sold as paid plans or as standalone plugins that share the Jetpack framework. Many sites run entirely on the free features, while others subscribe for managed security and backups.

How do I know if a site uses Jetpack?

The most reliable sign is images served from i0.wp.com, i1.wp.com, or i2.wp.com, which appear when Jetpack's image CDN is on. You can also check the page source and Network tab for assets loaded from /wp-content/plugins/jetpack/, Jetpack's stats tracking script, and module-specific markup like sharing buttons or related-posts blocks. Tools such as Wappalyzer confirm it, and curl -s URL | grep "i0.wp.com" works from any terminal.

What are the i0.wp.com domains?

i0.wp.com, i1.wp.com, and i2.wp.com are Automattic's image CDN hostnames. When Jetpack's site-acceleration feature is enabled, the plugin rewrites your content's image URLs to point at these domains, where the images are optimized, resized, and served from edge locations. Because no other common tool uses these specific hostnames in this way, seeing them in a page's HTML is a strong indication that the site runs Jetpack.

Does Jetpack require a WordPress.com account?

Most of Jetpack's features require connecting the self-hosted site to a WordPress.com account, because the plugin relies on Automattic's cloud for services like statistics, the image CDN, and security monitoring. This connection is what powers the externally hosted functionality. A small number of features can work without a full connection, but to use Jetpack as intended, the WordPress.com link is generally required.

Is Jetpack good or bad for performance?

It depends on how it is used. Jetpack's image and asset CDN can meaningfully speed up media-heavy sites by offloading delivery to Automattic's edge network, and lazy loading helps too. On the other hand, enabling many modules you do not need adds front-end scripts and overhead. For best results, turn on only the features you use and pair Jetpack with sensible caching. For broader guidance, see how to make your website load faster.

Want to detect Jetpack and the rest of a site's technology stack instantly? Run any URL through StackOptic at https://stackoptic.com.