https://docs.webp.se/Recent content in Introduction on WebP Cloud Services DocsHugo -- gohugo.iohttps://docs.webp.se/webp-cloud/basic/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/basic/Basic Usage # Dashboard is at https://dashboard.webp.se/login, we support login with GitHub only. Once you’ve logged in with GitHub, you can create your first Proxy. For example, if your image is at https://docs.webp.se/images/webp-wordpress.png, then you should fillin https://docs.webp.se in Proxy Origin URL field. After creation, you’ll find a new address, in the example below, it’s https://559a238.webp.ee. Now you can make request to https://559a238.webp.ee/images/webp-wordpress.png for a WebP optimized image. In order to change all your images url on website to new address, please refer to Access page.https://docs.webp.se/public-services/gravatar/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/public-services/gravatar/Gravatar Usage Examples # General # Change the link from https://www.gravatar.com/avatar/:hash to https://gravatar.webp.se/avatar/:hash. Wordpress # Edit your theme, and add the following code inside the functions.php: function use_webp_public_service($avatar) { $avatar = str_replace(array("www.gravatar.com", "0.gravatar.com", "1.gravatar.com", "2.gravatar.com"), "secure.gravatar.com", $avatar); $avatar = str_replace("https://secure.gravatar.com", "https://gravatar.webp.se", $avatar); return $avatar; } add_filter('get_avatar', 'use_webp_public_service'); like this:https://docs.webp.se/public-services/unavatar/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/public-services/unavatar/Unavatar Usage Examples # General # Change the link from https://unavatar.io/:anything to https://unavatar.webp.se/avatar/:anything.https://docs.webp.se/webp-cloud/access/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/access/Access # In order to use our service, you need to change all image urls on page from your original one(e,g https://yyets.dmesg.app/api/user/avatar/BennyThink) to the new one(e,g https://vz4w427.webp.ee/api/user/avatar/BennyThink), here are some ways to achieve this. All the examples below are using: Old URL: https://yyets.dmesg.app/api/user/avatar/BennyThink New URL: https://vz4w427.webp.ee/api/user/avatar/BennyThink Make sure to make necessary changes. Rewrite after build If you’re using static website builder, you can try using this script after running build command(e,g hugo --minify):https://docs.webp.se/public-services/github-avatar/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/public-services/github-avatar/GitHub Avatar Usage Examples # General # Change the link from https://avatars.githubusercontent.com/u/:id to https://avatars-githubusercontent-webp.webp.se/u/:id.https://docs.webp.se/public-services/availablity/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/public-services/availablity/Availability # Some of our Public Services are globally deployed and will ensure a lot lantency around the global, refer more on our blog post: Using Cloudflare Workers at the edge to enable services to source data from nearby locations – reducing global average latency Public Services # Service Name Endpoint USA Germany Singapore Unavatar https://unavatar.webp.se ✔ Unavatar Testing https://unavatar-dev.https://docs.webp.se/public-services/cache/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/public-services/cache/Cache # To ensure all images are served up to date, we cache all images for 1 day, cache will be purged on every day at 00:00 UTC.https://docs.webp.se/webp-cloud/feature/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/feature/Feature # Image Optimization # WebP Cloud will try to convert all your images to WebP/AVIF image and send the optimized image to your visitor(if the WebP/AVIF image is smaller), besides, by removing image metadata will make the image even smaller, and potentially reduce the risk of EXIF privacy leak. Original (1.73MB, PNG) Optimized (1.21MB, WebP) https://docs.https://docs.webp.se/webp-cloud/visual-effects/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/visual-effects/Visual Effects # Watermark # We support adding params on image to append watermark on it. Supported params are: text: Text to be added on image, need to be encoded in base64(url-safe). font: Font name, currently we support 11 fonts, see below for details, need to be encoded in base64(url-safe). color: Text color, in hex format, could be 6 chars(without transparency) or 8 chars(with transparent) width: Relative text width, in percentage from 0 to 1 height: Relative text height, in percentage from 0 to 1 offset_x: Relative text x position, in percentage from 0 to 1 offset_y: Relative text y position, in percentage from 0 to 1 We use __ to divide key and value, for example you want to temporarily add text Hello World on image, you can use text__SGVsbG8gV29ybGQ= as param.https://docs.webp.se/webp-cloud/cache/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/cache/Cache # Currently all the images will be cached and served from cache after first request, unless a “Purge cache” is triggered or cache space is full, thus it’ll have the following features: Works like “Always Online”, as long as the image cached, it can be normally rendered even if your Origin is offline. You can cache all your images by manually request them through proxy, this is so called “cache pre-heat” Cache status # From each proxy’s detailed page, you can see all the request logs, the Cache Status indicates whether an images is being rendered by WebP Cloud’s cache.https://docs.webp.se/webp-cloud/limits/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/limits/Limits # Image limit # Currently we can only support images with size less than 16383px * 16383px. Maximum file size is 80 MiB. Origin limit # Your origin must respond with content-type header and contains image. For example: Valid Header: content-type: image/gif Invalid Header: content-type: application/octet-streamhttps://docs.webp.se/webp-cloud/security/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/security/Security # Under dashboard’s Proxy detailed page, you will find a Security tab, which contains some security related settings, in short: Custom Proxy User Agent can be used as preshared key to origin Extra Origin Fetch Headers allows you to add more header when WebP Cloud fetch images from your origin, you can read more from our blog WebP Cloud now supports custom origin fetch headers Proxy CORS Header and Proxy Allowed Referer can help reduce your images being directly embedded on external websites.https://docs.webp.se/webp-cloud/quota/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/quota/Quota # Currently we run a request count quota based billing model, each free user will have 3,000 free requests per day. Quota will only count on successful image requests, and will be reset on 00:00 UTC+0 everyday. If you ran out of quota, images will be redirected to your original site(by default), see If I ran out of quota, what will happen? for details.https://docs.webp.se/webp-cloud/custom-domain/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/custom-domain/Custom Domain(Beta) # This feature is currently in beta stage and may encounter bugs🐛, please contact us immediately if you met them. Don’t you think the domain https://559a238.webp.ee/ is tooooo long for you, and you want to use your domain like https://webp.your-domain.tld? No problem! Currently if you want to use custom domain, you need to do the following: Create a new Proxy with same configuration, so the old address(xxxx.https://docs.webp.se/webp-cloud/api/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/api/API Reference # Note: API endpoints may subject to change without further notice The WebP Cloud API provides a standardized programmatic interface to access its infrastructure. To interact with the information available, you can make HTTPS requests to a specific version endpoint URL. The API supports various methods, including GET, POST, PUT, PATCH, and DELETE, which determine how you interact with the data. It’s important to note that all endpoints are accessible only through the SSL-enabled HTTPS protocol on port 443.https://docs.webp.se/webp-cloud/faq/Mon, 01 Jan 0001 00:00:00 +0000https://docs.webp.se/webp-cloud/faq/FAQ # Quota # If I ran out of quota, what will happen? # If you run out of your quota, all your Proxies will be disabled, and further requests will be redirected to origin by default. However you can change this behavior by setting Operation on Disabled in your Proxy’s settings, there are currently three options: Redirect Redirect means will 302 redirect to your original image Deny Deny means will send 403 to visitor Placeholder Placeholder will send a placeholder image to your vistor For example if you have a proxy with the following settings and Operation on Disabled set to Redirect: