Exact 300 kB target · Free · No upload
Compress Image to 300kB
Bring blog headers, product shots, newsletter banners and slide photos down to 300 kB with no visible loss – it all runs on your device and nothing is uploaded.
Files never leave your device — compression runs in your browser.
Drop your image here
or
JPG · JPEG · PNG · WEBP · HEIC* · GIF · BMP
- No upload
- 100% free
- Instant results
Working on your device — nothing is being uploaded.
Step by step
How to Compress Images to 300 kB
Three quick steps, no account and no app to install.
- 1
Upload Your Image
Drag a JPG, PNG, WebP or HEIC photo into the box above, click to browse, or paste it from your clipboard. The file opens on your device only — nothing is sent to a server.
- 2
Set the Target Size
The size box is already set to 300 kB on this page. Leave it as it is, or type any other number. Open Format & dimensions if your form also asks for a specific pixel size.
- 3
Compress and Download
Compression starts as soon as the file is added. Check the before/after preview and the exact byte count, then press Download. The file name tells you the final size.
Where this size shows up
When Do You Need 300 kB Images?
Anyone who wants to compress an image to 300 kB is almost certainly sending it to a web page, a product listing, an email or a slide – places where it has to look good at screen size but nobody will zoom in to the pixel level. That makes 300 kB a generous budget. A 1,200 to 1,600 px wide JPG fits inside it at a quality setting most people cannot tell from the camera original, and a WebP of the same size fits with room to spare.
On a website the number matters because of Core Web Vitals. Google's "good" threshold for Largest Contentful Paint is 2.5 seconds, measured at the 75th percentile of visits, and the 2025 Web Almanac found that the LCP element is an image on about 85% of desktop pages and 76% of mobile pages. The same survey puts the median mobile home page at about 911 kB of images and a typical inner page at around 354 kB. One 300 kB hero plus a handful of small graphics lands you right at that inner-page median, and three heroes still stay inside the home-page figure.
Shops have the same problem multiplied by the gallery. Shopify will accept files up to 20 MB, but six 3 MB product photos make an 18 MB page on a 4G connection, while six 300 kB shots are under 2 MB and still show stitching and texture at 1,500 to 2,000 px. In email the ceiling is even further away – Gmail and Outlook.com allow 25 MB per message – yet every inline image is base64-encoded, which adds roughly a third, so a 300 kB banner costs each reader about 400 kB. Mailchimp's own guidance is a maximum of 1 MB per image at 660 to 1,320 px wide, and 300 kB at 1,320 px is a comfortable fit.
Slide decks are the fourth big user of this size. A 16:9 slide is 1,920 × 1,080 px, and a 300 kB JPG at those dimensions looks crisp on a projector or a shared screen, so a 30-slide deck with a photo on every slide weighs about 9 MB instead of 90 MB and still goes through email. If your page is image-heavy or most of your readers are on mobile data, step down to 250 kB; for a portfolio piece or a hero shot on a retina display, the 350 kB option buys extra detail. A whole gallery at once? Use the bulk image compressor.
-
Blog and article images
Featured images and in-post photos at 1,200–1,600 px wide. Four of them at 300 kB keep a WordPress or Ghost post near 1 MB of pictures, well under the mobile home-page median.
-
E-commerce product photos
Main and gallery shots for Shopify, WooCommerce or marketplace listings at 1,500–2,000 px, so the zoom view still shows fabric weave and print detail.
-
Email newsletters
Header banners and promo images at 600–1,320 px wide. Inside Mailchimp's 1 MB guideline, and about 400 kB per reader once the mail system encodes it.
-
Slide decks
Full-bleed photos at 1,920 × 1,080 px for PowerPoint, Keynote or Google Slides, keeping a long deck quick to open and small enough to send.
-
Google Business Profile photos
Google accepts JPG or PNG between 10 kB and 5 MB with at least 250 × 250 px. A 300 kB upload at about 1,200 px looks sharp in Maps without a long load.
-
Landing-page hero images
The picture above the fold is usually the LCP element. A 1,600 px hero at 300 kB with fetchpriority="high" and no lazy-loading gives you a real shot at the 2.5-second mark.
Reference
Portals that ask for files around 300 kB
Typical limits from official notifications and help pages. Each row links to its source.
| Portal / purpose | Item | Size limit | Dimensions | Format | Source |
|---|---|---|---|---|---|
| Google Business Profile | Business photos (logo, cover, gallery) Any file between the two limits is accepted; 300 kB at about 1,200 px loads quickly in Maps and Search. | 10 kB – 5 MB | min 250 × 250 px | JPG, PNG | Official |
| Google Ads – uploaded display ads | Image ad creative Half this page's target. Use the 150 kB preset with exact dimensions for these. | 150 kB max | 300 × 250, 336 × 280, 728 × 90, 320 × 50 and other listed sizes | GIF, JPG, PNG | Official |
| Mailchimp | Images in email campaigns A recommendation rather than a hard block; 300 kB keeps the whole email light. | 1 MB max (recommended) | 660–1,320 px wide (new builder); 600–1,200 px (legacy builder) | PNG, JPG, GIF | Official |
| Shopify | Product and collection images A generous cap. 300 kB at 2,000 px is a page-speed choice, not a platform rule. | Under 20 MB | Up to 5,000 × 5,000 px (25 megapixels) | JPEG, PNG, WebP, GIF, HEIC and more | Official |
Limits change between recruitment cycles. Always confirm the numbers on the notification or form you are filling in before you upload.
Pro tips
Tips for Compressing to 300 kB
-
Pick the pixel size before the kilobytes
Decide where the image will sit and resize for that spot. Full-width blog or hero image: 1,600 px wide. In-post photo or product gallery: 1,200–2,000 px on the long side. Email banner: no more than 1,320 px, Mailchimp's upper figure, because the mail client scales it down anyway. Slide: 1,920 × 1,080 px. Open Format & dimensions, choose fit within that width, and the tool spends your 300 kB on quality instead of on pixels nobody will see.
-
WebP for your own site, JPG for everything else
Lossy WebP typically comes in 25–34% under an equivalent JPEG (Google's figures), and caniuse puts browser support at about 97% as of October 2026. On pages you control, 300 kB of WebP therefore carries a visibly larger or cleaner picture. Email clients, slide software and many marketplaces are less predictable, so leave the output on JPG there. Read the format comparison if you are unsure which case you are in.
-
Logos and screenshots: PNG, but watch the dimensions
Flat graphics with text, hard edges or transparency belong in PNG. Because PNG is lossless, the only way to make it smaller is to reduce its dimensions, so a 2,400 px screenshot may come back at 1,600 px to fit 300 kB. If the transparency is not needed, switch to JPG or WebP and keep the full width – just remember that transparent areas turn white in a JPG.
-
When a photo refuses to fit
A busy, high-detail photo – foliage, crowds, fabric patterns, a street scene – needs more bytes per pixel than a portrait against a plain wall. If the preview looks soft, do not force the quality lower. Let the tool take the dimensions down a step (it does this on its own once quality would drop below about 45%) or crop to the part that matters. A clean 1,400 px crop beats a blocky 2,000 px frame every time.
-
Doing a whole gallery or newsletter? Batch it
Set 300 kB once in the bulk image compressor, add up to 200 files, tick limit longest side and enter 1,600 px, then download the ZIP. Every file lands at or under the target with identical settings, so a product grid or a run of newsletter images looks consistent instead of varying from shot to shot.
Quality check
What to expect at 300 kB
Start with the arithmetic. 300 kB is 2.4 million bits, and the median JPEG on the web spends about 2 bits per pixel (HTTP Archive, 2024), so the budget covers roughly 1.2 megapixels – about 1,280 × 960 px – at a typical quality, and considerably more for smooth, low-detail pictures. A passport-style photo sits far below that line: a 600 × 600 px headshot saved at high quality is usually under 150 kB, so the tool will tell you it is already under 300 kB and hand back the original untouched. Only a full camera frame of a face needs work, and it returns at around 1,600–2,000 px tall with every eyelash still in place.
A document scan behaves differently, because text is all hard edges and JPEG spends its bytes on edges. An A4 sheet at a 150 dpi scan is 1,240 × 1,754 px (2.2 megapixels) and lands under 300 kB at a mid-range quality with every line readable; at 200 dpi (3.9 megapixels) the tool will usually have to scale the page down a notch, which is still fine for an online upload but not for reprinting. Lock the dimensions if a portal checks them, and expect faint JPEG speckle around the letters that does not affect legibility. A multi-page document is better handled as a PDF compressed to 300 kB, where the black-and-white option saves a lot.
A full phone photo is where 300 kB shows both its limits and its strength. A 12-megapixel shot at 4,000 × 3,000 px and 2–4 MB cannot keep all its pixels at this size without visible blocking, so the tool reduces it in high-quality steps – typically to about 1,600–2,000 px on the long side – and then searches for the quality that lands just under 300 kB. On a phone or laptop screen that version looks the same as the original; it only falls short if someone crops hard or prints larger than a postcard. The result panel shows the exact byte count, the final dimensions and the quality used, and the before/after slider lets you check for yourself.
Good to know
Frequently Asked Questions
Is 300 kB suitable for website images?
Yes, for almost everything except a downloadable print file. At 300 kB you can serve a 1,600 px wide header or a 2,000 px product photo at a quality the eye reads as original, so the size suits featured images, hero banners, product galleries and in-post photos alike. The reason to go lower is volume, not quality: a page with twenty 300 kB thumbnails is 6 MB of pictures before any script or font, and the median mobile home page already carries about 911 kB of images (HTTP Archive, July 2025). On dense pages keep 300 kB for the one big picture that forms the LCP element and take the small tiles down to 250 kB or less.
What image dimensions are best for 300 kB?
Around 1,200 × 800 px is the comfortable zone: a photo of any subject fits 300 kB at that size with quality to spare. Go to 1,600 × 1,067 px for full-width headers and 1,920 × 1,080 px for slides – most photos still land under the target at a good setting. Beyond that it depends on content. A sky, a studio portrait or a product on white has smooth areas that compress well and can run 2,000–2,400 px wide, while foliage, crowds, fabric patterns or a busy street cannot, and the tool will scale those down until the quality stays above roughly 45%. Set fit within to the width you actually display and let it sort out the rest.
Should I use JPEG or WebP for 300 kB web images?
WebP, when the image lives on a site you control. Google's measurements put lossy WebP 25–34% below a JPEG of matching visual quality, so the same 300 kB holds a larger or cleaner picture, and caniuse shows WebP working in about 97% of browsers in use (October 2026); add a JPG fallback with <picture> if you still support very old devices. Choose JPG when the file leaves the web: newsletters, slide decks, marketplace uploads and client hand-offs all take JPG without question, while some still reject WebP. The Auto setting in Mb2KbSizer follows the same logic – WebP in stays WebP, everything else becomes JPG – and you can override it under Format & dimensions.
Can I compress a 5 MB phone photo to 300 kB without it looking bad?
Yes. A 5 MB phone photo is usually 12 to 24 megapixels, and nothing on a web page, in an email or on a slide displays anywhere near that many pixels. Mb2KbSizer first tries to reach 300 kB by lowering the JPEG quality alone; when that would mean a blocky result (below roughly 45%), it shrinks the dimensions in clean steps – usually to about 1,600–2,000 px on the long side – and searches again until it lands at or just under 300 kB. That is a saving of about 94%, and the before/after slider lets you confirm that the difference is invisible at normal viewing size.
Will 300 kB images push my newsletter over an email size limit?
No. Gmail, Outlook.com and Yahoo Mail accept 25 MB per message and iCloud Mail 20 MB, so even ten 300 kB images – 3 MB, or roughly 4 MB after the base64 encoding that email applies to inline pictures – sit far inside those limits. The constraint that matters is the reader: images that download slowly on mobile data get scrolled past, and Mailchimp's own recommendation is a maximum of 1 MB per image. Keeping each picture at 300 kB and 600–1,320 px wide means the newsletter opens fully before the reader loses interest.
Do you store my images?
No. We have no image storage of any kind, because the file never reaches us in the first place. It sits in your browser's memory while you work, and the compressed version exists only on your device once you download it. Close or refresh the tab and both are gone. We keep no history, no gallery and no cache on our side, and we cannot see what you compress. Our web host records ordinary server logs, such as the time of a page visit and the browser used, but those cannot contain your pictures. For the full detail, read our privacy policy.
What is Mb2KbSizer and what does it do?
Mb2KbSizer is a free image and PDF compressor that runs inside your web browser. You pick a file, type the size you need, such as 100 kB, and it shrinks the file to land at or just under that number. Most people use it for upload forms that reject big files: exam registrations, passport and visa applications, job portals, bank KYC and college admissions. It is just as handy for lightening photos before you email them or put them on a website. There is a [single-image tool](/), a bulk compressor for up to 200 photos at once, and a PDF compressor, all built on the same no-upload principle.
Is Mb2KbSizer free to use?
Yes. Every tool on this site is free, and we intend to keep it that way. There is no sign-up, no premium tier, no daily quota and no watermark on the output. Compress one photo or three hundred; nothing counts against a limit. A few ads on the page pay for hosting. Because the heavy lifting happens on your own device rather than on our servers, each extra user costs us almost nothing, so there is no reason to charge. We do not sell an app, a plan or an API either, so you will never be nudged towards a paid version.
Do I need to install any app to use Mb2KbSizer?
No installation is needed. Mb2KbSizer is a web page, so it works the moment it loads in current Chrome, Edge, Firefox, Safari or Samsung Internet on a phone, tablet or computer. Nothing is downloaded to your device except the page itself, and it does not ask for storage or camera permissions. If you use the tool often, you can add it to your phone's home screen from the browser menu and it will open like an app. It still needs an internet connection to load, though, so treat this as a shortcut rather than an offline program. There is no Play Store or App Store version.
How do I compress an image using Mb2KbSizer?
Three steps, usually under a minute.
- Add your photo. Drag it onto the upload box, tap browse to pick it from your gallery, or paste it from the clipboard with Ctrl/Cmd + V.
- Set the target. Type a number and choose kB or MB, or tap a quick chip from 20 to 350 kB. On a preset page the field is already filled in. If a form demands exact pixel dimensions, set them in the resize option.
- Press Compress, then Download. You get a before/after slider, the output dimensions, the quality used and the exact byte count, so you know it will pass before you submit it.
What image formats does Mb2KbSizer support?
You can upload JPG, PNG, WebP, GIF (the first frame is used), BMP and AVIF, provided your browser can decode the file. HEIC photos from an iPhone open in Safari and other browsers with HEIC support; elsewhere the tool explains how to set the camera to Most Compatible so new shots are saved as JPG. Files up to 60 MB are accepted. For output, Auto gives a JPG in most cases and keeps WebP as WebP; you can also force JPG, WebP or PNG. PNG is lossless, so a PNG target is reached only by reducing dimensions, which is why JPG is the better pick for a small photo.
Is it safe to upload my images to Mb2KbSizer?
Strictly speaking, you never upload anything. When you choose a file, the browser reads it from your device and does the resizing and re-encoding in a background worker on that same device. No copy travels to our server or to anyone else's; the only thing our server sends you is the page. A useful side effect is that the browser rebuilds the image from its pixels alone, so EXIF data such as the camera model, the date taken and the GPS location is dropped from the output. That makes the compressed photo safer to share than the original you started with.
Sources & further reading
- web.dev – Largest Contentful Paint (LCP) thresholds
- web.dev – Optimize LCP (fetchpriority, no lazy-loading)
- HTTP Archive Web Almanac 2025 – Performance chapter
- HTTP Archive Web Almanac 2025 – Page Weight chapter
- HTTP Archive Web Almanac 2024 – Media chapter (bits per pixel)
- Google Developers – WebP, an image format for the web
- caniuse – WebP image format support
- Google Business Profile Help – Photo and video guidelines
- Google Ads Help – Upload image ads
- Mailchimp – Image recommendations for content blocks
- Shopify Help Center – Product media types
- Gmail Help – Attachment size limit
- Microsoft Support – Outlook.com attachment limits
- Yahoo Help – Attachment size limits
- Apple Support – iCloud Mail message size and Mail Drop
- MDN – Base64 encoding overhead