simpletool.io Browse tools

Tag: Image Tools

  • Make PDF Look Scanned: Browser-Only Converter [2026]

    Make PDF Look Scanned: Browser-Only Converter [2026]

    TL;DR: A “scanned PDF converter” makes a clean digital PDF look like it came out of a real scanner — adds skew (slight rotation), paper grain, faded ink, edge shadows, and downsamples to 96–150 DPI. Used for forms that demand “scanned” submissions, courtesy submissions where a printout-and-rescan would be the official process, and for visual consistency in workflows that mix scanned and digital documents. Our free scanned PDF converter runs entirely in your browser using pdf-lib + canvas filters.

    The “please submit as a scanned PDF” requirement is one of the small absurdities of digital paperwork. A perfectly valid digital signature is rejected by an HR system that still parses scanned forms only. A government portal expects an “ink-on-paper” feel even though the form was filled in Word. Some e-discovery systems flag clean PDFs as suspicious because they assume real submissions go through a copier. The fix: take your clean digital PDF and run it through filters that mimic the artefacts of a real scan — grain, skew, faded edges, slightly off-white paper.

    Our scanned PDF converter applies five effects in combination: skew (random ±2° rotation per page), grain (paper texture noise), ink fade (slight contrast reduction), edge shadow (vignetting from the scanner glass), and resolution downsample (rasterise to 150 DPI). The result passes most “looks scanned” detectors without any of the security concerns of uploading sensitive forms to an unknown server. This guide covers each effect, when to use this for legitimate workflows, and the legal grey areas to avoid.

    The 5 effects and what each fixes

    Effect Tells it fixes Default value
    Skew Perfectly aligned page edges ±1.5° rotation per page
    Paper grain Pixel-perfect text and uniform background 8% noise, low contrast
    Ink fade Pure black text, 100% saturation Reduce contrast 12%, RGB shift to #1a1610
    Edge shadow Razor-sharp page boundaries 12px gradient at edges, 30% opacity
    Resolution Vector-perfect text rendering Rasterise to 150 DPI
    Paper tint Pure white background #fdfaf2 (off-white)
    JPG compression Sharp PNG-grade quality JPG quality 80, slight blocking

    Three intensity presets

    Most users don’t need to tune individual sliders. The presets cover 95% of cases:

    • Light: subtle grain and skew, retains text crispness. For legitimate forms where the scanned look is a courtesy.
    • Medium (default): noticeable grain, ink fade, edge shadow. The “honest scan” preset.
    • Heavy: aggressive aging — strong grain, brown paper tint, more skew. For documents you want to look old or photocopied many times.

    Pick a preset, preview the first page, adjust if needed.

    How to make a PDF look scanned

    1. Open the scanned PDF converter
    2. Drop your PDF in
    3. Pick a preset: Light, Medium, or Heavy
    4. Adjust skew amount, grain intensity, paper tint, and resolution if needed
    5. Click Convert. Each page is rasterised, processed, and re-embedded
    6. Download the converted PDF — typically 2–4× the original file size due to raster pages

    Legitimate uses (and the line you shouldn’t cross)

    Legitimate:

    • Forms that demand a “scanned” submission for visual consistency (HR forms, some legal templates, some government portals)
    • Submitting a digital fill of a form designed to be printed-and-scanned
    • Visual consistency in mixed scanned/digital archives
    • Mock-ups for UI design (e.g., showing what a scanned doc looks like in a doc-management UI)
    • Educational examples of OCR pre-processing

    Don’t:

    • Forge documents — making a fake invoice “look scanned” to deceive someone is fraud, regardless of whether you used Photoshop or this tool
    • Pass off a generated document as having gone through a paper original — for any document that requires a wet-ink signature, use one
    • Strip metadata to hide the original source from a fraud investigation
    • Manipulate evidence — adding “scanned” artifacts to a document submitted in legal proceedings is evidence tampering

    The tool is for honest workflows. If your use case requires the recipient to believe the file went through a paper-and-scanner pipeline that it didn’t, you’re in fraud territory.

    Common gotchas

    • File size grows. Rasterising vector pages to images (even at 150 DPI) typically 2–4× the original file size. A 1 MB digital PDF becomes 2–4 MB scanned-look output. Run through a PDF compressor after if size matters.
    • Text becomes uncopyable. The output is image-based — selecting text returns nothing. Most workflows treat that as a feature (real scans are also image-based until OCR). If you need selectable text, don’t run this conversion.
    • Search engines and accessibility tools can’t read it. A converted PDF has no machine-readable text — which is fine for forms but bad for archival. Keep the digital original.
    • Skew direction. Use random ±skew per page, not constant ±skew. A constant tilt looks like a misaligned scanner, not a stack of slightly-misfed pages.
    • Paper colour. Pure white (#FFFFFF) is the giveaway — real scans land on slightly off-white because of paper colour, ambient light, or scanner sensor calibration. Even at “Light” preset we tint to #fdfaf2.
    • Line art. CAD drawings and line-art-heavy documents can look damaged after grain + downsample. Test before processing technical drawings.

    When NOT to use this tool

    For documents that require legal authenticity (contracts, medical records, court filings), skip the conversion — submit the original PDF if possible, or scan a printed copy of the wet-signed version. For OCR or text extraction, the conversion makes things worse, not better — keep the digital original. For batch processing (100s of files at scanned-look output), install pdf-lib + sharp locally and script the conversion. For sensitive material where even browser processing is too risky, use offline software like ImageMagick on an air-gapped machine.

    Frequently asked questions

    Why would I want to make a PDF look scanned?

    Forms that demand “scanned” submissions for visual consistency, government portals that flag clean PDFs, HR systems that only accept scan-style files, and visual consistency across archives that mix scanned and digital documents. Always for honest workflows — fabricating documents to deceive someone is fraud regardless of the tool.

    Will the converted PDF still have selectable text?

    No. The conversion rasterises each page, so the output is image-based. Selecting text returns nothing. Most workflows that demand “scanned” PDFs expect this — real scans are also image-based until OCR is applied. If you need selectable text, don’t run this conversion.

    How much does the file size grow?

    Typically 2–4× the original. A 1 MB digital PDF becomes 2–4 MB after raster conversion at 150 DPI. Run the output through a PDF compressor if size matters — a moderate compression brings it back close to the original size while keeping the scanned look.

    Is this legal?

    The tool itself is legal everywhere. The output’s legality depends on use. Submitting a converted file to a workflow that demands “scanned” format for visual consistency is fine. Using it to forge documents (fake invoices, fake official records) is fraud regardless of the tool.

    Is my PDF uploaded?

    No. The converter runs in your browser using pdf-lib + canvas. The file loads into a blob URL and never leaves your tab. You can verify in the Network tab — zero outbound requests after upload.

    Can I undo the conversion?

    No — once rasterised, the original vector text is gone. Always keep your digital original in a separate file. The converted file is a one-way derivative, not a wrapper around the original.

    Related tools and guides

     

  • Image Color Picker Tool: Sample HEX, RGB & HSL [2026]

    Image Color Picker Tool: Sample HEX, RGB & HSL [2026]

    TL;DR: An image color picker tool samples the exact colour of any pixel from an uploaded photo and converts it to HEX, RGB, HSL, and CMYK. Designers use it to extract brand palettes, match a website’s accent to a hero photo, or steal the perfect blue from a sunset shot. Our browser-based image color picker processes the photo locally — no upload, no signup, click anywhere on the image to sample.

    The fastest way to find a colour you can describe but can’t name: photograph it (or screenshot it) and run an image color picker over it. Brand designers do this with mood-board photos. Frontend developers do it when matching a CSS background to a hero image their team’s photographer captured. Print designers do it before specifying CMYK values for a poster run. The photo holds the colour information at full precision; an image color picker translates that into the format your CSS, design tool, or print spec actually uses.

    Our image color picker tool reads the photo via your browser’s canvas API and extracts the exact RGB values of any pixel you click. It outputs in HEX, RGB, HSL, HSV, and CMYK simultaneously, with one-click copy on each format. The photo never uploads — useful for proprietary brand work, NDA-protected mockups, or anything you’d rather keep off third-party servers.

    The five colour formats and when each is right

    Format Example Use for
    HEX #635BFF CSS, brand guidelines, design tools — the universal web colour notation
    RGB rgb(99, 91, 255) Programming (every image library uses RGB), some legacy CSS
    HSL hsl(244, 100%, 68%) Building palettes — easier to derive lighter/darker shades by adjusting one number
    HSV hsv(244, 64%, 100%) Photoshop and Affinity Photo’s default colour picker — useful for matching design files
    CMYK cmyk(61%, 64%, 0%, 0%) Print — magazine, brochure, business card. Different gamut from RGB; expect approximation

    Why HSL is the designer’s secret weapon. Once you have a colour in HSL, you can build an entire palette by changing only the lightness. hsl(244, 100%, 68%) with the lightness pushed to 90% becomes a soft tint suitable for a card background; pushed to 30% becomes a deep shade for hover states. RGB and HEX don’t expose this control as cleanly — adjusting them to a perceived lighter/darker version requires multiple channel changes that often shift the hue.

    The CMYK caveat. Computer screens use additive RGB; printers use subtractive CMYK. The two colour spaces don’t perfectly align — vivid screen blues, oranges, and greens often can’t be reproduced in print. The CMYK output from a screen-photo color picker is an approximation; for production print work, ask your printer for their colour-managed conversion (they’ll use ICC profiles to map RGB → CMYK accurately).

    Five common workflows for an image color picker

    • Brand palette extraction. Drop your company’s hero photo into the tool, click on the four or five distinctive colours. Save those as the starter palette for your design system.
    • Matching website accents to imagery. When a marketing photo dominates a landing page, the CTA buttons and section backgrounds look better when they pull from the photo’s palette. Sample from the photo first, then build the CSS.
    • Reproducing a competitor’s colour. Found a colour you like on someone else’s site or in a magazine? Screenshot, drop into the picker, copy the HEX. Faster than guessing and far more accurate than a paper colour wheel.
    • Print colour matching. Photograph a paint chip or fabric swatch under daylight, sample it, and use the result as the starting CMYK for a printed brochure. Calibrate against the actual print sample for accuracy.
    • Accessibility audits on photos. Sample the dominant colour of a photo behind text. Run the WCAG contrast check against your text colour. If it fails, you know exactly which photo region needs an overlay.

    How to use the browser image color picker

    1. Open the image color picker
    2. Drop your photo onto the dropzone, or click to pick from disk
    3. The image renders in a zoomable canvas. Use scroll-wheel or pinch to zoom in for pixel-precision sampling
    4. Click anywhere on the image to sample — the HEX, RGB, HSL, HSV, and CMYK values appear instantly with a swatch preview
    5. Click the copy icon next to any format to grab that exact value to your clipboard
    6. Sample additional pixels by clicking new locations — each sample stays in your history sidebar for easy comparison

    Everything happens client-side via the canvas getImageData API. The photo never uploads, the sampled colour never transmits.

    Sampling colours in code

    Browser JavaScript (canvas getImageData):

    const canvas = document.createElement("canvas");
const img = new Image();
img.crossOrigin = "anonymous";
img.onload = () => {
  canvas.width = img.naturalWidth;
  canvas.height = img.naturalHeight;
  const ctx = canvas.getContext("2d");
  ctx.drawImage(img, 0, 0);

  // Sample pixel at coordinates (x, y)
  const [r, g, b, a] = ctx.getImageData(x, y, 1, 1).data;
  const hex = "#" + [r, g, b].map(n => n.toString(16).padStart(2, "0")).join("");
  console.log(hex);
};
img.src = "/path/to/photo.jpg";

    Node.js (Sharp + raw pixel access):

    import sharp from "sharp";

const { data, info } = await sharp("photo.jpg")
  .raw()
  .toBuffer({ resolveWithObject: true });

const idx = (y * info.width + x) * info.channels;
const [r, g, b] = [data[idx], data[idx + 1], data[idx + 2]];
console.log(`rgb(${r}, ${g}, ${b})`);

    Python (Pillow):

    from PIL import Image

img = Image.open("photo.jpg")
r, g, b = img.getpixel((x, y))[:3]
print(f"#{r:02x}{g:02x}{b:02x}")

    The four mistakes that produce the wrong colour

    • Sampling JPEG artefact pixels. JPEG compression creates colour noise around hard edges. A pixel sampled at the boundary between a logo and its background often has a “halo” colour that doesn’t match either neighbour. Sample 10-20 pixels into the solid region.
    • Trusting screenshots over the source. If you screenshot a website to sample its CSS colour, your screen’s colour profile, your monitor’s calibration, and macOS/Windows’s gamma all shift the values. Use browser DevTools’ eyedropper directly on the live element instead.
    • Mixing up sRGB and Display P3. Modern Macs and iPhones photograph in Display P3 colour space, which encodes vivid colours that sRGB can’t reach. A picker that assumes sRGB on a P3 photo returns desaturated values. Most browser tools handle this automatically, but be aware when results look slightly off.
    • Sampling backlit or shadowed regions. A subject’s shirt looks bright pink in direct sun, dim pink in shade. The “real” colour exists somewhere in between — for brand work, photograph in even diffused light or sample multiple regions and average them.

    When NOT to use a single-pixel color picker

    • For palette extraction from complex photos. A single pixel doesn’t represent a photo’s overall colour story. Use a dominant-colour or palette-extractor tool that analyses the whole image. (We have one: the Image Color Extractor.)
    • For accessibility-grade colour matching. WCAG contrast calculations need precise colour values. A single sample can hit a JPEG artefact pixel; sample 20 and average for accuracy.
    • For print colour proofing. The CMYK approximation from a screen photo is rough. Order a printed proof or ask your printer for an ICC-managed conversion.
    • From low-resolution or heavily-compressed sources. A 200×200 thumbnail saved at JPEG quality 50 has bands of false colour everywhere. Source a higher-res copy if you need accurate colours.

    Frequently asked questions

    What’s the difference between an image color picker and a screen color picker?

    An image color picker samples colours from a static image you upload. A screen color picker (like Chrome DevTools’ eyedropper or macOS Digital Color Meter) samples colours directly from any pixel on your screen, including live web pages. For sampling a colour from a photo, image color picker. For sampling a CSS colour from a competitor’s live site, screen picker.

    Can I get the dominant colour of an entire image?

    Not from a single-pixel picker. Use our dedicated Image Color Extractor which analyses the whole image and returns the top 5-8 dominant colours plus a perceptual palette suitable for design systems.

    Why does my sampled HEX not match the colour I expected?

    Three common causes: (1) JPEG artefacts producing false colours near edges — sample further into solid regions; (2) your monitor’s calibration shifting how colours display; (3) the source photo using Display P3 colour space which encodes wider gamut than sRGB. For brand work, sample multiple pixels in the same region and use the median value.

    Is my photo uploaded when I use the picker?

    No. The browser reads the photo via the File API, draws it on a canvas, and reads pixel data from the canvas — all without making any network requests. Verify in DevTools’ Network tab. The photo and any sampled colours stay on your device.

    Can I sample colours from a website screenshot?

    Yes — drop the screenshot into the picker like any other image. For higher accuracy though, use Chrome DevTools or browser extensions that sample directly from the live page (avoiding screenshot compression). Both Chrome and Firefox have built-in eyedroppers in their colour pickers.

    Does the tool work on transparent PNGs?

    Yes. Transparent regions return alpha = 0 in the sample readout, with the underlying pixel colour shown for reference. If you click on a transparent pixel and want the colour you’d see (white if displayed on white), composite the image first or sample a non-transparent neighbour.

    Related tools and guides

     

  • Free Image Cropper Online: Aspect Ratio Presets [2026]

    Free Image Cropper Online: Aspect Ratio Presets [2026]

    TL;DR: A free image cropper online removes parts of a photo to fit an exact aspect ratio — Instagram squares (1:1), Stories (9:16), YouTube thumbnails (16:9), Twitter headers (3:1). Our browser-based image cropper ships ten ratio presets, freeform crop, rotation, and format conversion (PNG/JPEG/WebP). No upload, no signup, processed entirely on your device.

    Every social platform crops your image differently. Instagram wants a 1:1 square in the feed, 4:5 portrait for higher reach, 9:16 vertical for Stories and Reels. YouTube needs 16:9 thumbnails. Twitter clamps post images to a 16:9 viewport unless you click to expand. Upload a 4000×3000 photo to any of them and the platform crops it for you — usually wrong, often cutting your subject’s head off. A free image cropper online lets you do the cropping yourself, with the result you actually want.

    Our image cropper runs entirely in your browser. Drop the photo, pick a ratio preset (or freeform), drag the crop box to the right region, click Download. The cropped output saves in PNG, JPEG, or WebP at your chosen quality. Your photo never uploads — meaningful for ID scans, kids’ photos, and anything you’d rather not hand to a server. This guide explains the platform-by-platform aspect ratios, the rotation + format-conversion features, and the workflow tricks that make repeat cropping fast.

    Aspect ratios for every social platform in 2026

    Platform / Use Aspect ratio Notes
    Instagram square post 1:1 Default feed format; classic and reliable
    Instagram portrait post 4:5 Tallest format the feed accepts; gets more pixels visible per scroll → higher engagement
    Instagram Story / Reel / TikTok 9:16 Vertical full-screen; reserve top + bottom 200px for UI overlays
    YouTube thumbnail / cover 16:9 Pre-crop to exactly 1280×720 to avoid YouTube’s auto-recompression
    Twitter / X header 3:1 Profile photo overlaps bottom-left; keep critical content centered
    Facebook cover ~21:8 Mobile crops differently than desktop; safe zone is the centre 60%
    LinkedIn banner 4:1 LinkedIn enforces this aspect strictly
    Pinterest pin 2:3 Vertical performs ~2.3× better than square per Pinterest’s data
    Photo print 4×6 3:2 Standard photographic print and DSLR sensor ratio

    The most common mistake: uploading a 4:3 phone photo into a 1:1 Instagram square and letting the platform pick the centre crop. The result usually clips a subject’s forehead or chin. Crop to the platform’s native ratio yourself with our tool — you decide what gets included, not Meta’s algorithm.

    How to use the browser image cropper

    1. Open the image cropper
    2. Drop a photo (JPG, PNG, WebP, GIF, BMP, HEIC) into the dropzone, or click to pick from disk
    3. Pick a preset — Free, 1:1 Square, 4:3, 3:2, 16:9, 9:16, IG Post, IG Story, Twitter Header, YouTube Cover
    4. Drag the crop box to position it. Pinch on touch devices to zoom; scroll-wheel zoom on desktop
    5. Use the rotation buttons (90° increments) if the photo is sideways, or fine-tune with the slider
    6. Pick the output format — PNG (lossless), JPEG (smaller, photo-friendly), or WebP (smallest, modern)
    7. Set JPEG/WebP quality (85 is the web sweet spot) and click Download

    The crop happens entirely in your browser via the HTML canvas API. No file is transmitted, no cropped result lives on a server. Refresh the page and the photo is gone from memory.

    Format choice — PNG vs JPEG vs WebP after crop

    • JPEG quality 85: right answer for photographs in 95% of cases. Compresses to ~15% the size of an equivalent PNG with no perceptible quality loss. Use for photos uploaded to social media, websites, and email.
    • WebP quality 85: ~30% smaller than JPEG at equivalent quality. Supported everywhere modern (Chrome, Safari 14+, Firefox, Edge). Use for web delivery; some legacy systems and older email clients still don’t accept WebP.
    • PNG: for graphics with text, sharp edges, or transparency. Photos saved as PNG are ~5× larger than JPEG with no quality benefit. Don’t use for photos.
    • Original format: when you want the cropped output to match the source format exactly (preserving any specific format quirks the source had).

    The quality slider matters most for JPEG. At 85, photos look identical to the source. At 75, side-by-side comparisons reveal slight artefacts on detail-heavy regions but the average viewer doesn’t notice. At 60, compression artefacts become visible on skin tones and gradients. For social media uploads, the platform recompresses your image anyway — start at 85 to give the platform clean source material to work from.

    Rotation — the under-used feature that fixes most “bad” photos

    Phone photos taken in landscape orientation but stored with the EXIF rotation flag are a constant source of confusion. Some viewers honor the EXIF flag (showing the photo upright); some don’t (showing it sideways). Our cropper reads the EXIF orientation tag and applies it correctly before showing the photo, so what you see is what you’ll get on every platform.

    Beyond EXIF correction, manual rotation handles three common cases:

    • Slightly tilted horizons. A photo of the ocean with a 2° tilt looks “off” subconsciously. Our cropper has a fine-rotation slider for ±15° corrections.
    • Sideways scans. A document scanned upside-down can be rotated 180° before cropping the relevant region.
    • Aspect ratio fit. A wide landscape photo can be rotated 90° and cropped to portrait if you specifically need vertical orientation.

    Cropping in code — Sharp, Pillow, ImageMagick

    Node.js (Sharp — fastest production library):

    import sharp from "sharp";

// Crop to 1080×1080 from the top-left corner
await sharp("photo.jpg")
  .extract({ left: 0, top: 0, width: 1080, height: 1080 })
  .jpeg({ quality: 85 })
  .toFile("photo-square.jpg");

// Or use the smart resize-crop combo (centers automatically)
await sharp("photo.jpg")
  .resize(1080, 1080, { fit: "cover", position: "centre" })
  .toFile("photo-1080.jpg");

    Python (Pillow):

    from PIL import Image

img = Image.open("photo.jpg")
# Crop coords: (left, top, right, bottom)
cropped = img.crop((100, 50, 1180, 1130))
cropped.save("photo-square.jpg", quality=85, optimize=True)

    ImageMagick CLI:

    # Smart center crop to 1080×1080
magick photo.jpg -resize 1080x1080^ -gravity center -extent 1080x1080 photo-square.jpg

# Crop a specific region (1080×1080 starting at x=100, y=50)
magick photo.jpg -crop 1080x1080+100+50 photo-square.jpg

    For batch processing — say, cropping 500 product photos from a CSV of crop coords — Sharp on Node is the fastest approach. Sharp uses libvips under the hood and processes thousands of images per minute on commodity hardware.

    The four mistakes that ruin cropped photos

    • Cropping too tight on faces. Cutting the top of someone’s head looks bad on every platform. Leave 10-15% headroom in any portrait crop. The standard wedding/event photographer rule.
    • Wrong aspect ratio for the platform. Cropping to 1:1 then uploading to Pinterest (which prefers 2:3) wastes the platform’s algorithmic preference for your format. Match the ratio to the destination first.
    • Letting the platform crop instead. Auto-cropping algorithms pick the centre by default. If your subject is off-centre — common in Rule-of-Thirds composed photos — the platform will crop them right out of the frame.
    • Saving as PNG when JPEG would do. A 1080×1080 photograph saved as PNG is ~3 MB; the same as JPEG quality 85 is ~200 KB. Social platforms then recompress the PNG anyway. Skip the round-trip and save as JPEG to start.

    When NOT to crop

    • Legal evidence photos. Cropping changes the file’s metadata and visual extent — both attributes courts use to verify authenticity. Submit originals.
    • Anything documenting medical or scientific evidence. The framing is part of the data. If you must crop for size, archive the original separately with the crop coordinates documented.
    • RAW camera files (.cr2, .nef, .arw, .dng). Cropping a raw file loses the RAW container. Develop the RAW first in Lightroom, Capture One, or darktable, then crop the resulting JPEG/TIFF.
    • Photos with EXIF metadata you need to preserve. Standard browser cropping strips EXIF (location, camera model, aperture, shutter speed). Use a metadata-preserving tool like exiftool if the EXIF matters.

    Frequently asked questions

    Does cropping reduce image quality?

    Cropping itself doesn’t reduce quality — the cropped pixels are byte-identical to the source. Quality loss happens only if you re-encode the result as JPEG or WebP at a lower quality setting. Save at 85+ and the cropped image is visually indistinguishable from the source within the cropped region.

    Is my photo uploaded when I use the cropper?

    No. The browser reads the photo locally via the File API, the cropper renders it on a canvas in your browser tab, and the cropped output is offered as a download — all without making any network requests. Open browser DevTools Network tab and watch for upload requests when you click Download: there are none.

    What’s the maximum image size the cropper handles?

    Limited by your device’s RAM, not by us. A 50-megapixel raw smartphone photo (~15 MB) crops in about a second on a modern laptop. A 100-megapixel medium-format JPEG (~50 MB) might take 2-3 seconds. Server-based croppers cap at 10-25 MB; we have no upper limit because there’s no upload.

    Can I crop multiple photos at once?

    The current tool is one-at-a-time. For batch jobs, use Sharp or Pillow scripts (examples above). The browser tool is optimised for the case of “I have one photo and need it in a specific shape” — the most common social-media workflow.

    Will the cropper preserve transparency in PNGs?

    Yes if you save as PNG or WebP. JPEG output flattens transparency to white because JPEG doesn’t support transparency. If your source has transparency you want to keep, choose PNG or WebP for the output format.

    Can I crop a circle or non-rectangular shape?

    The cropper outputs rectangular images only — that’s what every social platform actually accepts. For circular profile photos, social platforms apply the circle mask themselves at display time, so a square crop is what you upload. If you need actual circular images for design work (with transparent corners), use a vector editor like Figma or Illustrator after cropping to square.

    Related tools and guides