In order for HTML and Javascript to work, it has to be intrepreted by their computer, and even if you do find a way to disable 'View Source' there are others ways, like a DOM inspector ( F12 in IE/Chrome, Ctrl+ Shift+ K in Firefox).Īs a workaround, use copyright, warn your users they will be punished if they copy your code, and put watermarks, labels and logos over any mp3s or images you don't want stolen. If you upload an image and prevent users from downloading it, they can take a screenshot or use their camera. If you post a song to the internet, even if they cannot find the mp3, they can simply record their speakers. However, these things all use code, and code can be decrypted through any number of methods. You can definitely make HTML and JS harder to intrepret by obfuscating your code - that is, taking your code and making it look confusing. Take a leaf from their book and don't stress that they copy your HTML. There's very little relative value in the generated HTML that you see in the page.

The value is in the algorithms that execute on the server when you hit that Google Search button that queries that data and returns the information you're looking for. Why not? Because the value of the search engine isn't in what the home page looks like, but in the data on the back-end that you don't have direct access to. If what you have on your page is so important that others shouldn't be able to see it, don't put it on a webpage.įinally, Google doesn't much care that you're able to view the source to their home page. I'd suggest that you don't worry about it.

You could try to encrypt it, but if it's using local data to decrypt itself, there still isn't going to be anything that stops them from just copying what's in the View Source window and running it again (even if they can't really read it). You expressed an urge to prevent your friends from copying the source code. Now, a web page is a relatively simple container for holding information. Have you heard of DRM? It's a mechanism that companies like to try to use to control how people can connect to their services, use their content and in general, try to exert control over their data while it's on your system. This is an issue that larger companies deal with often.

As a rule, if you are putting information on another user's computer (whether because you made a document or they viewed your webpage), you really can't control what they do with it.

View s in chrome