Service Account & Credits
Connect a free GetWebP account, understand WordPress service credits, and verify that image files stay in the browser-local optimization path.
Service Account & Credits
GetWebP for WordPress uses a free GetWebP account connection to manage site authorization, optimization credits, and job status. The current admin UI requires the site to be connected before scanning, previewing quality, or saving optimized files.
This account connection is for the control plane. Image bytes stay in the browser-local WordPress optimization path.
Table of Contents#
- Why the Account Connection Exists
- Connect a Site
- What Is Sent to GetWebP
- What Is Not Sent
- Credits and Plans
- Refresh or Disconnect
- If Connection Fails
Why the Account Connection Exists#
The free WordPress plugin does not require a license key, but it does require a GetWebP service account connection before optimization work can start.
The connection lets GetWebP:
- authorize the WordPress site
- show current credit usage and reset timing
- reserve credits before a batch writes generated files
- complete or refund service jobs when a browser-side run finishes or fails
It does not turn WordPress image conversion into a hosted image-upload service.
Connect a Site#
- Open GetWebP in WordPress admin.
- Click Connect free account.
- Sign in to GetWebP.
- Authorize the WordPress site.
- Return to WordPress and confirm the dashboard shows the connected account and credit status.
If the browser cannot return automatically to WordPress, use the manual token shown by GetWebP and paste it into the WordPress connection screen.
Connect each WordPress site or multisite subsite that will run optimization.
What Is Sent to GetWebP#
Service calls may include control-plane metadata such as:
- site and account token state
- site URL and plugin version
- local attachment IDs or source keys
- source MIME type, byte size, width, and height
- requested outputs, preset, and run mode
- job reservation, completion, refund, and idempotency information
This metadata is used for account connection, credit accounting, and job lifecycle handling.
What Is Not Sent#
GetWebP does not receive:
- original image files
- decoded pixels
- generated WebP or AVIF files
- full WordPress upload folders
During optimization, the administrator's browser reads eligible files from your own WordPress site, encodes outputs locally, and sends generated files back to the same WordPress site through authenticated admin requests.
Credits and Plans#
The free WordPress account includes:
| Limit | Free account |
|---|---|
| Monthly optimized images | 100 |
| Images per browser batch | 20 |
| License key required | No |
| Service account connection required | Yes |
Credits are consumed when generated files are saved for a Media Library source image. Quality preview does not consume credits because it writes no generated files.
For current paid plan details, see Credits & Plans and getwebp.com/pricing.
Refresh or Disconnect#
Use the GetWebP dashboard to refresh account and credit status after changing plans, resetting a connection, or resolving a network issue.
Disconnecting removes the local service account connection for that WordPress site. Generated files already saved in uploads remain in place until you delete optimized copies or undo a run.
If Connection Fails#
Check:
- The WordPress admin page can reach
https://api.getwebp.com/. - Pop-ups or strict browser privacy settings are not blocking the sign-in return flow.
- Security plugins, firewalls, or proxies are not blocking WordPress admin AJAX requests.
- The manual token flow works if automatic return is blocked.
- The connected site URL matches the WordPress admin site you are using.
After resolving the issue, refresh the GetWebP dashboard and try the connection again.