2025/11/19

Your Images Are Being Uploaded: Privacy Risks of Online Image Tools

Most online image tools upload your photos to their servers. Learn why this matters, what data they collect, and how to identify tools that process images locally. Real privacy analysis with practical recommendations.

The Question That Made Me Investigate

A few months ago, a graphic designer I know sent me a link to an online image tool and asked: "Is it safe to use this for client work?"

My first reaction was "probably fine." Then I actually thought about it. She was merging product photos for an unreleased line - images that hadn't been made public yet. If she used an online tool that uploaded those images to a server somewhere, who else might see them?

That question sent me down a rabbit hole of privacy policies, terms of service, and browser developer tools. What I found wasn't reassuring.

The Default: Your Images Leave Your Computer

Here's what most people don't realize: when you use most online image tools, your images aren't processed on your computer. They're uploaded to a server, processed there, and the result is sent back to you.

This seems obvious in retrospect, but I'd never really thought about it. Upload your images, merge them, download the result. Simple workflow, right?

The problem is what happens during that upload step.

What I Discovered Testing Popular Tools

I tested 10 popular online image tools using browser developer tools to watch network traffic. Here's what I found:

Tools that upload your images:

iLovePDF
Smallpdf
Aspose
Online-Image-Tools
Fotor
Canva

Tools that process locally (images never leave your browser):

MergeJPG
IMGonline.com.ua
PhotoJoiner

That's 60% of tools uploading your images. Maybe that's fine for casual use, but it matters more than I thought.

Why Image Uploads Matter

Scenario 1: Client Work

A photographer I know was editing wedding photos. She used an online tool to merge images vertically for album layouts. Those were her clients' private wedding photos - uploaded to a server in who-knows-where, processed by who-knows-what, stored for who-knows-how-long.

When I mentioned this to her, she went pale. "I never thought about that."

Most tools claim they delete images after processing. Maybe they do. But you're trusting them with sensitive client data based on a promise in a privacy policy.

Scenario 2: Unreleased Products

I talked to a product manager at an e-commerce company. They were merging product photos for an upcoming launch. The products hadn't been announced yet - this was confidential pre-release stuff.

He'd been using a popular online tool that uploads images. When security asked him where those images had been sent, he had no answer.

"Some server somewhere, I guess. The tool says they delete them immediately."

Security was not happy with that answer.

Scenario 3: Medical Photos

A dermatologist was creating before/after comparisons for patient records. Before/after photos showing faces, skin conditions, treatment areas.

He was using an online tool that uploaded to their servers. Those were HIPAA-protected patient photos being sent to a third-party service that may not be HIPAA-compliant.

This isn't a theoretical risk - it's a compliance violation.

What Actually Happens When You Upload

I spent time reading privacy policies and terms of service for major image tools. Here's what I learned:

The Optimistic Case

What they claim:

Images are encrypted during upload
Processed immediately and automatically
Deleted from servers within 1-24 hours
Not used for any other purpose

iLovePDF says: "Files are automatically deleted from our servers after a few hours."

Smallpdf says: "We delete your files permanently after one hour."

This is the best-case scenario, and it's probably what actually happens most of the time.

The Less Optimistic Reality

But here's what the terms of service also say:

From a popular tool's TOS (paraphrased):

We may use uploaded content to improve our services
We may aggregate and analyze usage data
We comply with legal requests for data
We're not responsible for unauthorized access to your files
Service is provided "as is" without warranty

So even in the best case:

Your images exist on their servers temporarily
They might be analyzed (not clear if this means viewing)
If their server is compromised, your images might be too
If they receive a legal request, they might have to provide your images

The Unknown

And here's what we don't know:

Are images really deleted after processing?
Are deleted images actually wiped, or just marked as deleted?
Who has access to images during processing?
Are images encrypted at rest on their servers?
Where are the servers located (jurisdiction matters for privacy laws)?

For most tools, you have to trust their privacy policy. You have no way to verify what actually happens.

The Alternative: Local Processing

Some tools process images entirely in your browser using JavaScript. Your images never leave your computer.

How This Works

When you use a tool like MergeJPG, here's what happens:

You select images from your computer
They're loaded into your browser's memory
JavaScript code in your browser merges them
The result is generated in your browser
You download it from your browser's memory

At no point do your images hit a server. The tool's website serves the HTML/CSS/JavaScript code, but your actual images stay local.

You can verify this:

Open browser developer tools (F12)
Go to the Network tab
Upload images and merge them
Watch the network traffic - you'll see no large file uploads

Why Tools Upload Images

If local processing is possible, why do most tools upload images to servers?

Reason 1: Easier to build Server-side image processing is simpler to develop. Most image libraries are designed for servers, not browsers.

Reason 2: More powerful Servers can handle larger files and more complex processing than browsers.

Reason 3: Business model Some tools analyze uploaded images for business intelligence or use them to train AI models. Local processing doesn't enable this.

Reason 4: Cross-device syncing Cloud storage requires server uploads by definition.

These are valid reasons, but they come at the cost of your privacy.

Red Flags to Watch For

Based on my research, here are warning signs that a tool might not respect your privacy:

Red Flag 1: Unclear Privacy Policy

If you can't easily find or understand their privacy policy, that's a problem.

Good example (from a tool I tested): "Your images are processed entirely in your browser and never uploaded to our servers."

Bad example: "We take your privacy seriously and comply with all applicable laws."

The second one tells you nothing useful.

Red Flag 2: Required Account Registration

If a tool requires you to create an account just to merge two images, ask yourself why.

Account registration enables:

Tracking what images you process
Associating your images with your identity
Email marketing
Usage analytics tied to your account

For simple image merging, account registration shouldn't be necessary.

Red Flag 3: "Free" Tools with No Clear Business Model

If a tool is free and has no ads, how are they making money?

Possible answers:

Freemium model (they want you to upgrade)
Data collection (they're selling insights from uploaded images)
Loss leader (they make money on other products)
Legitimate passion project

The first and third are fine. The second is concerning. The fourth is rare.

Red Flag 4: Vague Terms About Data Usage

From a tool I tested: "We may use uploaded content to improve our services and develop new features."

What does "improve our services" mean? Are they:

Analyzing image types to prioritize which formats to support? (Fine)
Running face detection to build training data? (Not fine)
Collecting metadata? (Depends what for)

Vague language usually means "we want maximum flexibility to use your data."

Red Flag 5: No HTTPS

If the website isn't using HTTPS (check for the padlock in your browser), your images aren't encrypted during upload.

This is rare in 2025, but I've still seen it on older tools.

How to Identify Tools That Process Locally

Here's how I test tools before trusting them with client work:

Method 1: Check the Network Tab

Open browser developer tools (F12 in most browsers)
Go to the Network tab
Clear the network log
Upload images and process them
Look for large file uploads (your image files)

If you see your images being uploaded (large POST requests), the tool uses server processing.

If you don't see uploads, it's likely processing locally.

Method 2: Turn Off Internet

Upload your images
Turn off your internet connection (disconnect WiFi)
Try to process/merge them

If processing works with no internet, it's definitely local. If it fails, it needs server access.

This works for MergeJPG - you can load the page, then disconnect and still merge images.

Method 3: Read the Privacy Policy

Look for explicit statements like:

"Processed entirely in your browser"
"Images never leave your device"
"No server uploads required"
"Client-side processing only"

If you can't find clear language about this, assume images are uploaded.

Method 4: Check File Sizes

If the tool has file size limits, that might indicate server processing.

MergeJPG has a limit of 20 images but no file size limit, because everything processes in your browser. Your computer's RAM is the limit, not server bandwidth or storage.

Tools with strict file size limits (like "5MB per image") are often uploading to servers with storage constraints.

Real-World Privacy Incidents

I couldn't find confirmed cases of image tools leaking user data, but here are relevant cautionary tales:

Face App (2019): A photo editing app uploaded user photos to Russian servers. Users realized their photos were leaving their devices, raising privacy concerns. The company claimed photos were deleted, but users had no way to verify this.

Clearview AI (2020): A company scraped billions of photos from social media to build a facial recognition database. While not directly related to image tools, it shows what can happen when images become data.

Privacy International research (2021): Found that many "free" apps collect and sell user data far beyond what users expect or consent to.

The lesson: when images leave your device, you lose control over them.

When Server Upload Is Actually Necessary

I'm not saying server-based tools are always bad. Sometimes they're the right choice:

OCR (text recognition): Complex OCR requires significant processing power and training data, making server processing practical.

Advanced AI editing: Tools that use AI to remove backgrounds, enhance resolution, or generate content usually need server-side processing.

Collaboration: If multiple people need to access the same images, server storage makes sense.

Very large files: Raw photos from professional cameras (50-100MB each) might exceed browser processing capabilities.

The key is knowing when upload is necessary vs. when it's just convenient for the tool developer.

Practical Recommendations

Based on everything I've learned, here's what I actually do:

For Client Work or Sensitive Images

Use tools that process locally:

MergeJPG for image merging
Browser-based tools that explicitly state local processing
Desktop software (GIMP, PhotoScape) that works offline

Avoid:

Any tool that requires upload for basic operations
Tools with unclear privacy policies
Free tools with suspicious business models

For Personal/Public Images

Server-based tools are probably fine:

Social media posts
Public website images
Memes, screenshots, non-sensitive content

The privacy risk for public images is minimal since you're publishing them anyway.

For Testing a New Tool

Before using with real images:

Check the privacy policy for clear local processing language
Use browser developer tools to verify no uploads
Test with dummy images first
Turn off internet and test if processing still works

For Specific Use Cases

Medical/legal photos: Only use tools you can verify process locally, or use desktop software

Pre-release products: Local processing only

Client work: Get client consent if using server-upload tools, or stick with local processing

Wedding/event photos: Local processing recommended

Social media content: Server-based tools fine

What MergeJPG Does Differently

Full disclosure: I work on MergeJPG, so I'm biased. But here's why we built it this way:

Local processing by design: All image merging happens in your browser using JavaScript and HTML5 Canvas API. Your images never touch our servers.

No account required: You don't need to register, log in, or provide any personal information.

No tracking: We don't track what images you process or how you use the tool.

Open about limitations: Because we process locally, we can't handle extremely large files (100+ megabytes) or hundreds of images at once. That's the tradeoff for privacy.

Verifiable: You can use browser developer tools to confirm nothing is uploaded. You can also disconnect your internet after loading the page and the tool still works.

This approach isn't unique to us - other tools do this too. But it's increasingly rare as tools move to cloud-based architectures.

The Business Reality

Here's the uncomfortable truth: privacy-focused tools are harder to monetize.

Server-based tools can:

Collect usage analytics
Gather training data for AI/ML
Analyze trends in uploaded content
Upsell cloud storage
Require subscriptions for processing power

Local-processing tools can't:

They can't see what you're processing
They can't analyze your images
They can't upsell features that require servers
They're limited by your device's capabilities

This is why most tools use server processing even when client-side processing would work. It's a business decision, not a technical one.

Questions to Ask Before Using Any Tool

Before I use an online image tool (for anything beyond throwaway screenshots), I ask:

Where do my images go?
- Are they uploaded to a server?
- If so, where is that server located?
What happens to them?
- Are they processed immediately?
- How long until they're deleted?
- Can I verify deletion?
Who might see them?
- Do employees have access during processing?
- Could they be accessed if the server is compromised?
- Could they be provided to law enforcement?
What's the business model?
- If it's free, how does the company make money?
- Do they sell data or insights?
Can I verify the claims?
- Does local processing actually work?
- Does the privacy policy match reality?

If I can't answer these questions confidently, I don't use the tool for sensitive images.

Conclusion

Most online image tools upload your photos to their servers. For random screenshots or public images, this probably doesn't matter. For client work, unreleased products, medical photos, or anything sensitive, it absolutely does matter.

The solution isn't to avoid online tools - it's to understand what they're doing with your images and choose accordingly.

For sensitive images: