Safari (Apple), saves web pages in a webarchive format, the filename extension: .webarchive

@boxing: Thank you but webarchive (to the best of my knowledge) is ~Apple proprietary just like MHT is Microsoft proprietary.

Could I ask why this would be a problem? thanks.

Archiving a website is honestly a bit too complicated for it to be universal and accessible. Most web sites serve up slightly different content for different types of viewers, browsers, operating systems, etc. It’s kind of a dead end if you’re looking to make a living snapshot of a website that can be sent as if it were a package and then viewed on another browsers, especially since AJAX technologies have become so popular. I think these are the primary reasons why there isn’t really a universal format for archiving the content of a site.

I’ve honestly never had an issue switching between MHT or .webarchive files, you just need to know a bit about the client recieving it.

@boxing: It is a problem because I try to avoid proprietary formats where possible. Of course a person could successfully live their whole life and never run a program that wasn’t written by Microsoft so it isn’t a problem in the sense that it won’t work.

@noyesa: Since I have control of the website I can avoid technologies which make archiving impossible. The javascript within the page can generate slightly different content for different types of viewers, browsers, operating systems, etc. instead of the server.

Understood. But let’s just say it isn’t practical to avoid both formats totally for now. Proprietory can become universal, by the way. Some one has to come up with a technology first.