WebP to XBM Converter
Convert WebP to XBM in your browser. WebP files usually come from websites, Chrome's Save image as, CDNs and Android apps; XBM is the better fit for X11 cursors, icons and C programs that embed bitmaps. You get a 1-bit X BitMap (C source), black and white at 50% brightness or dithered if you choose. Nothing is uploaded.
- Processed locally
- No upload, no wait
- No sign-up
- No watermark
Drop images here
or choose files · paste with Ctrl/⌘ V
WebP expected · other image formats also work
How to use WebP to XBM
- 1
Add your WebP files: drop them here, choose them, or paste from the clipboard.
- 2
Pick the colour that replaces transparent areas, since XBM has none.
- 3
Click Convert. Each file is decoded and encoded in a background thread on this device.
- 4
Download the .xbm files one at a time or together as a ZIP.
Why use Aback Images for webp to xbm
Where the XBM goes next
XBM opens in X11 utilities, GIMP, ImageMagick and XnView.
XBM next to WebP
Both formats are lossy, so the size mostly follows the quality setting; at the default the XBM usually lands in the same range as the WebP.
A second lossy pass
WebP is lossy already, since it stores lossy VP8 coding or lossless VP8L, so keep the quality at or above the default to avoid stacking a new layer of artefacts on the old one.
Processed on your device
Your images are decoded, edited and encoded inside this browser tab by Web Workers. Nothing is uploaded to a server.
WebP vs XBM
What changes from WebP to XBM
Encoding: the WebP uses lossy VP8 coding or lossless VP8L; XBM uses none: bits written as hexadecimal bytes in C source, and the download is a 1-bit X BitMap (C source), black and white at 50% brightness or dithered if you choose.
Bit depth: 8 bits per channel in the WebP; XBM allows 1 bit per pixel, and the XBM written here has 1 bit per pixel.
Colour: RGB; lossy WebP stores colour at half resolution (4:2:0) in the WebP; XBM supports two colours, foreground and background, written here as pure black and white.
Transparency: the WebP stores it as a separate alpha plane, available in lossy as well as lossless files; the XBM has none, so transparent areas are filled with the colour you choose.
Animation: ANMF frame chunks, each with its own delay and blending; the XBM holds one image, so only the first frame is converted.
Metadata: the WebP can carry EXIF, XMP and ICC chunks; XBM can carry the #define names for width, height and an optional hotspot, but nothing is copied across.
About WebP
WebP is Google's web image format. It supports lossy and lossless compression, transparency and animation, and is typically 25 to 35 percent smaller than JPEG at the same visual quality.
A WebP is a RIFF file: 'RIFF', a length, 'WEBP', then chunks. A simple lossy file is one VP8 chunk and a lossless one is VP8L; the extended VP8X header announces alpha, animation, ICC, EXIF or XMP chunks.
WebP files usually come from websites, Chrome's Save image as, CDNs and Android apps.
About XBM
XBM is the 1-bit image format of the X Window System, written as C source code so it can be compiled straight into a program. It was used for cursors, icons and window decorations, and early web browsers displayed it.
An XBM file is C code: '#define name_width 16', '#define name_height 16', optional x_hot and y_hot lines, then 'static unsigned char name_bits[] = { 0x00, ... };' with each byte holding eight pixels, least significant bit first.
When converting WebP to XBM makes sense
XBM is the better choice for X11 cursors, icons and C programs that embed bitmaps, while WebP suits images on websites and in apps.
XBM strengths: Plain text that compiles into C programs; Tiny for small icons. Drawbacks to weigh: Black and white only; Large as text for big images; Dropped by modern browsers.
Limitations
- A lossy WebP converted to another lossy format pays twice: detail VP8 already dropped stays gone, and the new encoder drops more.
- WebP images saved from websites are often already resized and compressed for the page, so the result cannot be sharper than that copy.
- XBM holds two colours only, so the picture is reduced to black and white at 50% brightness, or with dithering if you turn it on.
- XBM is plain C source text, so large images make large files; it is meant for icons, cursors and line art.
- Only two colours survive the conversion.
More conversions
Related tools
Convert XBM to WebP in your browser, ready for images on websites and in apps. Batch, private, no uploads.
Convert WebP to JPG in your browser, with transparency filled in a colour you pick. Batch, private, no uploads.
Convert WebP to PNG in your browser, ready for screenshots, logos, graphics and anything that needs transparency. Batch, private, no uploads.
Convert WebP to GIF in your browser, with the animation kept frame for frame. Batch, private, no uploads.
Shrink JPG, PNG, WebP, AVIF and GIF files with MozJPEG, OxiPNG and modern codecs, with a live before/after preview.
Resize to exact pixels, a percentage or a longest side, with Lanczos3 and Magic Kernel resampling. Batch ready.
Strip EXIF, GPS, XMP, IPTC and comments losslessly. Pixels are never re-encoded for JPG, PNG and WebP.
Convert between 34 image formats in bulk: HEIC, WebP, AVIF, JPEG XL, PNG, JPG, GIF, TIFF, SVG, ICO, PSD, RAW and more.
Frequently asked questions
Does converting WebP to XBM lose quality?
XBM is lossy, so detail the eye barely notices is discarded to save space. The WebP was lossy already, so keep the quality high to avoid stacking artefacts.
What happens to transparency when converting WebP to XBM?
WebP stores transparency as a separate alpha plane, available in lossy as well as lossless files. XBM has no alpha channel, so transparent pixels are composited onto a solid colour, white unless you pick another. To keep transparency, convert to PNG, WebP or AVIF instead.
Will my animated WebP stay animated?
No. XBM holds a single image, so only the first frame is kept. Convert to animated WebP, APNG or GIF to keep the motion, or export every frame with the GIF Frame Extractor.
Which apps open XBM files?
X11 utilities, GIMP, ImageMagick and XnView. It does not open in web browsers.
Are my images uploaded anywhere?
No. Processing happens inside your browser with WebAssembly and Web Workers. The site only downloads the app code and codecs; your files never leave your device. You can confirm this with the live upload counter on the tool, or in your browser's network panel.
Can I process many files at once?
Yes. Drop a whole selection or folder. Files are processed in parallel on several worker threads, each result can be downloaded on its own, and everything can be saved as one ZIP.
Is it free? Is there a file limit or watermark?
It is free with no account, no watermark and no daily limit. The only limit is your device's memory: very large images (over roughly 100 megapixels) may be refused to keep the tab from crashing.