autocropper.io

AutoCropper accepts JPEG, PNG, TIFF, PDF, and HEIC uploads, and it works with pages captured on a flatbed scanner or shot with a phone. Any page that contains several photos — an album page, a loose pile of prints, or a binder sheet of trading cards — can be dropped in, and the tool runs in your browser with no download or installation. The free tier allows 5 scans a day with no signup.

Accepted upload formats

The upload area lists five supported formats:

If your page is already one of these, you can upload it directly. The tool does not require you to convert a phone photo to a scan first — a HEIC shot of an album page is treated the same as a flatbed TIFF.

Supported scan sources

AutoCropper is built for pages that hold more than one photo. The site names three source types explicitly:

• Album pages — a scanned or photographed page with several prints mounted on it.
• Loose photo piles — multiple prints laid out and captured in one frame.
• Trading-card binder sheets — a binder page of baseball or other cards, which the tool can split into individual card images.

Either capture method works: a flatbed scanner or a phone camera. The site's guidance is that "any page with several photos on it works," so the deciding factor is whether the page contains multiple distinct images, not which device produced it.

What happens after upload

Once a page is in, a detection algorithm draws a numbered box around each photo within seconds. You can drag, resize, or rotate any box before exporting. On export, each photo is saved as its own full-resolution file named after the source page — for example, album_04.jpg comes back as album_04_1.jpg through album_04_4.jpg. The site states exports are made with no compression, so the individual crops keep the quality of the original scan.

Limits and conditions to know before you start

• Free tier: 5 scans per day, no signup required. A pricing page exists at autocropper.io/pricing, but the free allowance above is what the site states on its main page.
• Browser-based: nothing to install; processing happens online rather than in a desktop app.
• Input must be a multi-image page. A single photo on a page is not the intended use case — the value comes from splitting one page into several files.

If your files are in one of the five listed formats and your page holds multiple photos, you can upload it as-is and expect a set of separate, full-resolution image files back.

You can cut most images to a fraction of their original file size without any visible quality loss by doing three things in the right order: resize the image to the dimensions it will actually display at, pick the right format for the content, then apply compression at a quality level that survives a side-by-side check. The single biggest mistake is skipping step one — an oversized image compressed at maximum quality is still far heavier than a correctly sized one.

Why file size and quality are a trade-off, not a fixed setting

Every compressed image is a negotiation between three variables: how many pixels you keep, how precisely each pixel is described, and how much the format is allowed to guess.

• Dimensions decide how many pixels exist at all. Halving width and height removes 75% of the pixel data before any compression happens.
• Quality level decides how aggressively the encoder discards detail it thinks you won't notice.
• Format decides the kind of discarding allowed — some formats throw away color precision, others only remove redundancy.

Because these interact, "quality 80" means something different on a 4000px photo than on a 600px thumbnail. Tune dimensions first, then quality.

Pick the format before you touch the quality slider

Practical rule: photos → JPEG or lossy WEBP; flat graphics and transparency → PNG or lossless WEBP; anything vector → SVG.

The four levers, in the order you should pull them

1. Resize to display size (biggest win, zero quality cost)

If your layout renders an image at 800px wide, serving a 2400px original wastes roughly 89% of the pixels. Resize to the largest size it will ever be displayed at, and add a 2× version only if you need retina sharpness.

2. Choose the format

Match the format to the content type using the table above. Converting a photographic PNG to JPEG or WEBP alone can shrink it by 80% or more.

3. Set the quality level

For JPEG and lossy WEBP, most photographs hold up well between quality 70 and 85. Below ~60, banding appears in skies and blur around text. Above ~90, file size climbs steeply for gains nobody can see.

4. Strip metadata

EXIF data, camera info, and embedded thumbnails can add tens of kilobytes. Remove them unless you specifically need copyright or orientation data — and note that stripping orientation can rotate an image, so verify after export.

When lossy compression is fine, and when it isn't

Lossy is acceptable when:

• The image is a photograph or has natural texture.
• It's decorative or below the fold.
• Slight softening won't be noticed at final display size.

Use lossless or vector instead when:

• The image contains text, UI elements, or thin lines (lossy creates ringing artifacts).
• It's a logo, icon, or diagram — SVG or PNG keeps edges clean.
• It will be edited again later; repeated lossy saves compound degradation.
• It's a screenshot of code or a chart where color accuracy matters.

Compressing vs. resizing: don't confuse them

Compressing reduces the bytes needed to describe the same pixels. Resizing reduces the number of pixels. They're independent, and resizing usually delivers the larger saving. A 3000×2000 photo at quality 95 might be 2 MB; the same photo resized to 1200×800 at quality 80 might be 180 KB. Doing only the quality reduction gets you maybe 40% off; doing both gets you over 90%.

A repeatable workflow

1. Determine the maximum display width in your layout (inspect the element or check your CSS).
2. Export at that width (plus a 2× variant if needed).
3. Convert to the right format — WEBP as a modern default, JPEG as a fallback, PNG/SVG for graphics.
4. Apply quality 75–85 for lossy formats and compare against the original.
5. Strip metadata and re-check orientation.
6. Verify before publishing (see below).
7. Serve the right file with srcset so small screens don't download the large variant.

How to verify quality before you publish

• View at 100% at final display size, not zoomed in — artifacts you can't see at real size don't matter.
• Toggle between original and compressed in a viewer or an online compressor's before/after preview.
• Check the worst-case areas: skies, smooth gradients, sharp edges, and any text.
• Compare file sizes and ask whether the extra kilobytes buy visible improvement. If not, go smaller.
• Test on a mid-range phone, where banding and blur are often more obvious than on a desktop monitor.

Common mistakes

• Compressing a full-resolution image and calling it optimized.
• Using PNG for photographs.
• Setting quality to 100 "to be safe" — it inflates size with no visible benefit.
• Re-saving a JPEG repeatedly, stacking artifacts each time.
• Forgetting that GIF animations are usually better as WEBP or video.
• Ignoring metadata, which can silently add weight.

Quick reference

The order matters more than any single setting: resize, then choose format, then tune quality, then strip metadata, then verify at real display size. Follow that sequence and you'll routinely land at 10–20% of the original file size with no quality your visitors can detect.

AutoCropper is a browser-based tool that takes a scanned page containing several photos and turns it into separate, full-resolution image files. You upload a scan, its detection algorithm outlines each photo on the page, and you export them individually. It fits best when you already have scans of album pages, loose photo piles, or card binder sheets and want each photo as its own file without manual cropping. The site states a free tier of 5 scans a day with no signup required; the presence of a Pricing page indicates paid options exist, but no prices or plan details are given in the available material.

The core workflow

The tool is built around a three-step process described on the site:

1. Start with existing scans. Any page with multiple photos works — album pages, loose photo piles, or a binder page of baseball or trading cards, whether scanned on a flatbed or photographed with a phone.
2. Upload and let detection run. The AI draws a numbered box around each photo within seconds. You can drag, resize, or rotate any box before exporting.
3. Download each photo separately. Export saves every photo as its own full-resolution file, named after the source page — for example, album_04.jpg comes back as album_04_1.jpg through album_04_4.jpg.

A sample scan is available on the site to try the process before uploading your own files.

What it handles well

• Multiple photos per page. The custom detection algorithm identifies each crop area rather than treating the page as one image.
• Straightening. Detected photos are straightened, which matters for phone photos of album pages taken at a slight angle.
• Batch processing. The site advertises splitting multiple scans at once and batch-exporting the results.
• No compression on export. The site states full-size scans come back at full quality.
• File types. JPEG, PNG, TIFF, PDF, and HEIC are accepted.
• No install. Everything runs in the browser.

The site reports over 3,000,000 scans processed, which is a usage claim from the vendor rather than an independent measure.

Where it fits and where it doesn't

Practical things to know before starting

• Scan quality drives results. Detection works on visible photo edges, so pages where photos overlap heavily or blend into the background may need manual box adjustments — the tool allows dragging and resizing for this reason.
• Naming is automatic. Output files inherit the source page name with numeric suffixes, so name your scans meaningfully before uploading if file organization matters.
• The free tier is a daily limit, not a one-time trial. Five scans per day, resetting daily, per the site.
• Check the Pricing page for anything beyond the free tier. The available material does not list plan prices, limits, or payment methods, so verify current terms there before relying on it for regular work.

If your task is "I scanned twenty album pages and need each photo as a separate file," AutoCropper is designed for exactly that job and you can test it on the sample scan first.

AutoCropper turns one scanned page containing several photos into individual image files by detecting each photo, drawing an adjustable box around it, and exporting every box as its own full-resolution file. It works on album pages, loose photo piles, and card binder sheets from either a flatbed scanner or a phone photo, and the free tier allows 5 scans a day with no signup. Use it when you already have multi-photo scans and want separate files without manual cropping; if your source images are already single photos, there is nothing to split.

What you need before starting

• A scan or photo of a page that contains more than one photo — album pages, loose photo piles, or a binder page of trading cards all work.
• A file in JPEG, PNG, TIFF, PDF, or HEIC format.
• A browser. Processing happens online, and the site states no download or install is needed.

Step-by-step: from one scan to many files

Step 1 — Start with the scans you already have

Any page with several photos on it is a valid input. The site notes this includes pages scanned on a flatbed or shot with a phone. If you are still producing the scans, the site links to separate guidance on scanning photos in bulk, so the split quality depends on how cleanly the photos are laid out on the page.

Step 2 — Upload and let detection outline each photo

Drag and drop your scans onto the upload area or use the file chooser. The detection step draws a numbered box around each photo within seconds. This is the core mechanism: a custom image detection algorithm identifies each crop area rather than you drawing rectangles by hand.

Step 3 — Adjust the boxes before export

Detection is a starting point, not a final answer. You can drag, resize, or rotate any box before exporting. Do this when a box clips a photo edge or includes part of a neighboring photo — a common issue on tightly packed album pages or tilted phone shots.

Step 4 — Download each photo as its own file

Export saves every photo as a separate full-resolution file, named after its source page. For example, album_04.jpg comes back as album_04_1.jpg through album_04_4.jpg. The site states exports are made with no compression, so the individual files keep the quality of the original scan.

What the output looks like

Common sticking points

• Boxes that are slightly off. Fix them in Step 3 with drag, resize, or rotate rather than re-scanning.
• Photos touching or overlapping on the page. Detection may merge or split them incorrectly; manual box adjustment is the remedy.
• Daily limit reached. The free allowance is 5 scans a day; the site also has a pricing page if you need more volume.
• Expecting edits to the photos themselves. AutoCropper detects, crops, straightens, and splits — it is not a retouching tool.

When this workflow fits

Choose AutoCropper when you have batch scans of multi-photo pages and want separate, full-resolution files quickly in the browser. Skip it when your images are already individual photos, or when you need per-photo color correction and restoration — those tasks belong in a different tool.

AutoCropper has a free tier that covers light use: the site states you get 5 scans per day with no signup and nothing to install, and you can process images in your browser. That is enough to test the tool on a few album pages or card sheets. For anything beyond occasional use, AutoCropper links to a separate Pricing page, but the site does not publish the plan details, limits, or prices in the material available here — so the only reliable way to compare paid options is to open that page directly.

What the free tier actually gives you

The free offer is defined by three things on the site:

• 5 scans per day. A "scan" is one uploaded page, not one photo. Since the tool splits a page into multiple files, a single scan can produce several cropped photos.
• No signup required. You can drag and drop a file and see results without creating an account.
• Browser-based processing. There is nothing to install.

The site also offers a sample scan you can run through the live demo before uploading your own files, which is a low-risk way to check whether detection handles your material well.

What counts against your 5 scans

Because the limit is per scan rather than per output image, the free tier stretches further than it first appears. One scanned album page with four photos uses one scan and returns four separate files. If your work is a handful of pages at a time, the daily cap is unlikely to bind. If you are digitizing a box of loose photos or a binder of trading cards, you will hit the limit quickly and need to either spread the work across days or look at the paid option.

What the paid plans add

The site's navigation includes a Pricing link, which confirms a paid tier exists. However, the available page content does not list plan names, prices, scan limits, batch sizes, or any quality differences between free and paid use. Two things follow from that:

• Do not assume the paid plans differ only in volume. The site markets batch splitting and full-resolution export as core features, and the free tier already describes full-resolution output. Whether paid plans add higher limits, larger batches, or other capabilities is not stated in the material here.
• Check the Pricing page before committing to a workflow. If your project depends on processing many pages in one sitting, confirm the paid limits there rather than planning around the free cap.

How to decide

A practical approach: run one or two of your own pages through the free tier first. If the numbered detection boxes land correctly on your photos and the exported files meet your quality needs, the free tier answers the question for light use. Only then does the paid tier become a question of volume — and that answer lives on the Pricing page.