Updated: July 17, 2026
To compress images for Notion, resize each file to the largest dimensions you actually need, export photos as WebP or JPEG, keep PNG or lossless WebP for text-heavy or transparent graphics, and inspect the output at 100% zoom before uploading. Free Plan uploads are capped at 5 MB per file. For paid plans, Notion's documentation is less clear: the help page's image section references a smaller PNG/JPG display limit, while the same page's FAQ and the pricing page describe a general upload limit of around 5 GB. If you see an "image too large to display" message, use the smaller target, check the current in-app guidance, or add the asset as a file block instead.
A browser-based compressor such as LessMB can process supported image formats locally in your browser — the source file is not sent to a compression server — making it a straightforward first step before you upload anything to Notion.
Key Takeaways
- Compress before you upload. Compressing in advance gives you control over file size and quality, and helps avoid upload errors on any plan.
- Free Plan: every file must be under 5 MB. For paid plans, Notion's official documentation contains conflicting figures; when in doubt, aim well below 5 MB for images.
- Resize first, then compress. Reducing an oversized image to the width you actually need often removes more bytes than any encoder setting alone.
- Match format to content. WebP or JPEG for photos; PNG or lossless WebP for transparent graphics and text-heavy screenshots. Notion supports WebP, JPEG, PNG, GIF, SVG, HEIC, and TIF/TIFF.
- Verify before uploading. Check file size, open the file at 100% zoom to confirm quality, and then upload.
Why Compress Images Before Adding Them to Notion?
Every image embedded in a Notion page must be fetched by each person who opens that page. Large source files mean longer upload times, slower initial loads on mobile connections, and a higher chance of hitting an upload error. On the Free Plan, every uploaded file — regardless of type — must stay under 5 MB, and the practical advice on the Notion help page points to smaller targets for image blocks even on paid plans.
Because there is no publicly documented guarantee about whether or how Notion reprocesses uploads after they reach the server, compressing upstream is the most reliable way to control what anyone downloading your page actually receives.
What Image Size Does Notion Allow?
Notion's official documentation contains a known inconsistency, noted here as of July 2026. Always check the current in-app error messages and the Notion help center for the latest guidance.
| Plan | General file upload | Image block note | What to do if you see an error |
|---|---|---|---|
| Free | Under 5 MB per file | Under 5 MB | Compress the file, then retry |
| Plus and above | ~5 GB per file (pricing/FAQ page) | Help page references smaller PNG/JPG display limit | Compress to well under 5 MB; check in-app prompt; or embed by URL |
Why Notion's Official Limits Appear Inconsistent
The Notion help page's image section and its FAQ/pricing page reference different numbers for paid plans. One reasonable interpretation is that "image display" in a page block may have a separate threshold from a general file upload. Until Notion clarifies the distinction officially, the safest workflow is to compress all images to a reasonable size regardless of plan, so the limit — wherever it sits — is never a concern.
Notion officially supports these image formats: JPEG/JPG, PNG, GIF, SVG, WebP, HEIC, TIF/TIFF (source).
How to Compress an Image for Notion in Five Steps
Step 1: Resize to the width you will actually display
Most images arrive far wider than they will ever appear on a Notion page. Reducing pixel dimensions is often the single biggest lever for shrinking file size.
The following widths are practical starting points, not Notion requirements:
- Full-width image: 1,600 px
- Standard body image: 1,200 px
- Thumbnail or inline icon: 400–600 px
Scaling down to these widths before compressing allows the encoder to work with far less data.
Step 2: Choose the right format
| Content type | Recommended format | Notes |
|---|---|---|
| Photos, gradient screenshots | WebP | Generally more compact than JPEG at comparable quality; supported in Notion |
| Photos (broad compatibility) | JPEG | Universally supported, well-established quality/size trade-off |
| Transparent graphics | PNG or lossless WebP | Compare both outputs; choose the smaller one that looks correct |
| Text-heavy screenshots | PNG or high-quality / lossless WebP | Compare at 100% zoom — JPEG artifacts can blur text edges |
| Simple icons or line art | SVG | Infinitely scalable at near-zero file size when vector art is available |
WebP is generally efficient for photos, but no single format is optimal for every image. Compare the output at 100% zoom and choose the format that gives you the best balance of visual quality and file size for that specific image.
Step 3: Compress with a trusted tool
- Squoosh — Google's free in-browser app. Drag in an image, compare codecs side by side, and download the result. Squoosh processes images locally in your browser (source: Squoosh GitHub), so the file is not sent to a remote server. Best for one or a few images where you want precise control.
- LessMB — Free browser-based compressor that runs locally; no file upload to a compression server. Useful for a quick compress-and-compare before uploading to Notion.
- TinyPNG / Tinify — Online compression for PNG, JPEG, and WebP. Check the current Tinify pricing and limits page for up-to-date free-tier batch limits, as these may change.
- ImageOptim (macOS) — Drag a folder onto the window; the app strips unnecessary metadata and applies lossless or lossy compression across PNG, JPEG, and GIF. Supports batch processing.
- FileOptimizer (Windows) — Batch optimizer supporting many formats; configure compression engines from the settings panel.
Step 4: Batch-process a folder safely
For a large folder of images, a command-line approach can save time. If you choose to use cwebp from Google's WebP tools, keep the following safety precautions in mind:
- Back up the originals first. Run any batch script on a copy of the folder, not the originals.
- Write outputs to a separate directory to avoid overwriting source files.
- Avoid up-scaling. The
-resizeflag incwebpwill enlarge images that are already smaller than the target. Only apply a resize target to images you have confirmed are larger than that dimension. - Test on one file first. Confirm the result looks correct before processing the entire folder.
A safer pattern — write outputs to a dedicated subfolder and skip files that are already under the target width:
mkdir -p notion_ready
for f in *.jpg *.jpeg *.png *.JPG *.JPEG *.PNG; do
[ -f "$f" ] || continue
cwebp -q 80 "$f" -o "notion_ready/${f%.*}.webp"
done
This version does not automatically resize, which avoids unintentional up-scaling. Resize in your image editor first if needed. Quality 80 is a starting point, not a guaranteed outcome; inspect the results and adjust.
If a script feels risky for your workflow, ImageOptim (macOS) or FileOptimizer (Windows) offer the same batch processing through a drag-and-drop interface.
Step 5: Verify before uploading
Run through the following checklist before every upload:
- File size is within the limit for your Notion plan (confirm in-app)
- Pixel dimensions match the largest size you will display
- Image opened at 100% zoom — text is sharp, gradients are smooth, no obvious artifacts
- Transparency renders correctly (for PNG/lossless WebP)
- File saved to a clearly named location so you don't re-upload the original by mistake
Practical Starting Targets by Image Type
These are editorial starting points — not Notion requirements or guaranteed results. Actual file sizes vary by image content, encoding settings, and tool.
| Image role | Starting width | Suggested format | Rough size target | When to use a larger size |
|---|---|---|---|---|
| Full-width hero | 1,600 px | WebP | 200–500 KB | High-detail photography for a showcase page |
| Body screenshot | 1,200 px | WebP or PNG | 100–300 KB | When text legibility requires lossless encoding |
| Inline diagram | 800 px | SVG or PNG | under 100 KB | Complex vector art not available as SVG |
| Thumbnail | 400 px | WebP | under 50 KB | Rarely needed larger than this at thumbnail scale |
Total page payload matters as much as any single file. A page with many images will load more slowly regardless of individual file size.
Format Decision Guide
| Your image contains | Start with | If it looks wrong, try |
|---|---|---|
| Photo or gradient | WebP (quality 80) | JPEG (quality 85) |
| Text and screenshot | PNG | Lossless WebP, compare at 100% |
| Transparent background | Lossless WebP or PNG | — |
| Simple icon / line art | SVG (preferred) | PNG |
Common Mistakes to Avoid
- Uploading unmodified camera or phone exports. A high-resolution photo from a modern phone can be many megabytes before any editing. Resize and compress before uploading.
- Using PNG for full-color photos. PNG is lossless and produces large files for photographic content. Switch to WebP or JPEG.
- Ignoring unnecessary metadata. Embedded EXIF data, color profiles, and thumbnail previews add bytes without contributing to how the image looks on a Notion page. Most compression tools strip this automatically; verify in your tool's settings.
- Over-compressing text screenshots. Heavy lossy compression makes text edges fuzzy. Keep text-heavy screenshots as PNG or use high-quality or lossless WebP, then compare at 100% zoom.
- Checking quality only in the Notion preview. The editor preview may show a scaled-down version. Always inspect the source file at 100% zoom before uploading.
When Should You Embed an Externally Hosted Image?
If an image is impractical to compress usefully — a high-resolution map, a detailed infographic, or an asset that must stay at full resolution — you can embed it by URL instead of uploading it. Use /image → Embed link and paste a direct URL to the hosted file.
When embedding by URL:
- The file is served from the external host, not uploaded to Notion's storage.
- The image depends on the external host staying available and the URL remaining valid.
- If the external host goes down or the URL changes, the image will not appear.
- Confirm that the external host permits direct linking and that the URL is publicly accessible.
This approach is supported by Notion's image block documentation (Notion help), though the exact behavior may differ from an uploaded asset.
FAQ
Should you compress images before uploading them to Notion?
Yes. Compressing before upload gives you direct control over file size and visual quality. Free Plan users must keep every uploaded file under 5 MB. For paid plans, Notion's documentation includes conflicting figures — the image section references smaller limits while the FAQ and pricing page describe a much higher general limit. Compressing in advance helps avoid upload errors and reduces the amount of data each page visitor must download.
What is the maximum image size for Notion?
Free Plan: every uploaded file must be under 5 MB. For paid plans, Notion's general upload limit is described as approximately 5 GB on the pricing page, but the help page image section references a smaller limit for PNG/JPG display. If you see an "image too large to display" error, compress the image, check the current in-app guidance, or embed it by URL using the /image → Embed link option.
What image format is best for Notion?
For photos and gradient screenshots, WebP or JPEG is generally a good starting point. For transparent graphics or text-heavy screenshots where sharpness matters, compare PNG and lossless WebP at 100% zoom and choose the smaller file that still looks correct. Notion supports JPEG/JPG, PNG, GIF, SVG, WebP, HEIC, and TIF/TIFF (source).
How do I fix "This image is too large to display" in Notion?
Resize the image to the largest dimensions you actually need, compress it as WebP or JPEG, confirm the output file is well within the limit shown in your workspace, and re-upload. If the image genuinely needs to stay large, host it externally and embed it by URL instead.
Can I upload WebP images to Notion?
Yes. WebP is an officially supported format, listed alongside JPEG/JPG, PNG, GIF, SVG, HEIC, and TIF/TIFF on the Notion help page.
How do I compress many images at once for Notion?
For a small batch, open each file in Squoosh for browser-local, server-free compression. For entire folders, use ImageOptim on macOS or FileOptimizer on Windows. If you use the cwebp command line, always back up originals, write outputs to a separate directory, and test on one file first — see the safe batch usage note in the article above.
Next Steps
- Open one image-heavy Notion page and note the file sizes of the largest embedded images.
- Download the originals, resize to the width you actually display, and export as WebP or JPEG.
- Run through the upload checklist: file size, 100% zoom quality check, transparent areas if applicable.
- Re-upload the compressed versions and confirm they upload without error.
- Adopt a single compression tool and a consistent target-width convention so new uploads stay manageable by default.
Sources
- Notion Help Center — Images, files & media — Upload limits, supported formats, and image block behavior (verified July 2026)
- Notion Pricing page — General file upload limits by plan
- Squoosh — Google's in-browser image compressor
- Squoosh GitHub repository — Confirms local, browser-side processing
- TinyPNG / Tinify — Online PNG, JPEG, and WebP compression; see current limits at tinypng.com/developers
- ImageOptim — macOS batch image optimizer
- FileOptimizer — Windows batch optimizer
- Google cwebp documentation — WebP encoder flags and usage
- Google WebP tools download — cwebp and related utilities