Skip to main content

Blogger Magic - Securing My Pictures From Being Copied

Every week, we see the naive query
How do I prevent my pictures from being copied?
and this, I regret to say, is a magic trick that has yet to be perfected. Others ask
Why does Google let people publish blogs with pictures stolen from other blogs?
and here, we have to note that Google has no interest in controlling blog content, beyond the limits of their own TOS regulations.

Each of us is responsible for ensuring that our content - that we own - remains ours.

Google doesn't do this for us. They aren't legally, morally, or socially responsible for controlling duplication of blog / website content, until the owner of any blog or website reports a problem. And even when a problem is reported, they have to consider both sides of the story.

Protecting our blog content is our responsibility.

Some well meaning helpers will tell you of free software that blocks context menu (right mouse click) "Save Image As". That software is written as JavaScript. Many folks, like me, explicitly block JavaScript from "" and other untrusted domains, using Firefox and NoScript, for personal security. Blocking scripts from untrusted domains is a normal component in layered security, on our computers.

Besides the fact that you can't effectively block the context menu "Save Image As" command, you can't control what's stored on my computer.

If your blog is viewed on my computer, it's my content.

I've written about cache, here and there. Cache is a basic feature in Internet design. It lets us view the same web site (blog) repeatedly, without requiring that the same content be downloaded from the server repeatedly. If you're viewing this article using your browser, it's cached in your browser.

If your computer is on a large network, it's possible that your computer connects to the Internet through a caching proxy server. If your ISP offers enhanced bandwidth, it's possible that they cache content too.

If I added a picture to this article, it would be cached, along with the text that you are reading. The right software can search and retrieve any cached content, from any cache. Anybody who needs to "steal" your pictures just needs the right software, and he can steal them right out of cache.

Anybody can make a screen print.

Besides blocking the "Save Image As" wizard, and from prohibiting caching, you'll face a third challenge. What's on my screen can be copied. Screen printing is very popular software. Print the screen, crop everything but the picture of interest, and there it is. Save it, and you have it. Display the picture full size, print that, and you have the full size copy.

How about watermarking the pictures? Put the URL of the web site in the corner. You can do this using IrfanView, PhotoShop, and a few more image processing programs. But watermarks are just bits. What you can take out, I can put back, with more software. And watermarks make the pictures ugly. They are as bad as the broadcast TV commercials at the bottom of the screen.

You can copyright your pictures - but can you enforce the copyright?

Finally, you are entitled to copyright your content. There are some free copyright "protection" services too. Register your content, and it's protected. But no, the Internet reaches all over the world.

Can you afford the lawyers, that will practice in every nation worldwide, and enforce your copyright? If your content / pictures are being pirated on a Blogger / Google hosted web site, you may be able to get action from a DMCA Complaint - but note the warnings, carefully.

Face it - once you publish a picture in your blog, it too is like a dandelion. It's out of your control.

Sorry. Magic only goes so far.


Tina said…
Thanks Chuck. Have you posted about the blocking javascript business? I guess I need to find out about it.
Nitecruzr said…

Actually, in researching the context menu blocking was where I realised its limitation. I may yet write about it. I bet if you try, you can find it mentioned in Blogger Help Forum: How Do I?, too.
Vikram Madan said…
Talking about stolen, why doesn't blogger do anything about content being stolen from blogger blogs using automated tools?

For example, there are some websites that will immediately show captcha if some IP address loads pages too fast.

I believe google groups have some kind of a protection against things being stolen.

So why not blogger? Can you do something about this??

Nitecruzr said…

If I surf to your blog, I download the content of your blog to my computer. As soon as your blog content hits my computer, I have your photos.


There is nothing that you can do about that. Read about cache.
Vikram Madan said…
Hi Chuck,

What you say is correct. But I am not talking about a few pages being loaded in one session.

But I am talking about full blogs being ripped by automated tools.

Why cant CAPTCHA be implemented? Some websites show you CAPTCHA if you load pages TOO FAST.

Google groups has mechanisms to prevent content theft.

So why not blogger?

Popular posts from this blog

Adding A Link To Your Blog Post

Occasionally, you see a very odd, cryptic complaint I just added a link in my blog, but the link vanished! No, it wasn't your imagination.

What's The URL Of My Blog?

We see the plea for help, periodically I need the URL of my blog, so I can give it to my friends. Help! Who's buried in Grant's Tomb, after all? No Chuck, be polite. OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

Embedded Comments And Main Page View

The option to display comments, embedded below the post, was made a blog option relatively recently. This was a long requested feature - and many bloggers added it to their blogs, as soon as the option was presented to us. Some blog owners like this feature so much, that they request it to be visible when the blog is opened, in main page view. I would like all comments, and the comment form, to be shown underneath the relevant post, automatically, for everyone to read without clicking on the number of comments link. And this is not how embedded comments work.