|Initial release||November 15, 2011|
|Operating system||Fire OS|
|Available in||English, Spanish, French, Italian, Japanese, Chinese|
The browser uses a split architecture where some of the processing is performed on Amazon's servers to improve webpage loading performance. It is based on the open source Chromium project that uses the Blink engine.
For each webpage, Silk decides which browser subsystems (networking, HTML or page rendering) to run locally on the device and which to run remotely on its own Amazon EC2 servers.
Silk uses Google's SPDY protocol to speed up loading of web pages. Silk gives SPDY performance improvements for non-SPDY optimized websites if the pages are sent through Amazon's servers. Some early reviewers found that cloud-based acceleration did not necessarily improve page loading speed, most notably on faster connections or for simpler web pages.
Some privacy organizations raised concerns with how Amazon passes Silk traffic via its servers, effectively operating as an Internet service provider for those using the browser. The Silk browser includes the option to turn off Amazon server-side processing. On July 26, 2016 it was reported that Silk prevents access to Google over HTTPS, but that bug has since been fixed.
Amazon says "a thread of silk is an invisible yet incredibly strong connection between two different things", and thus calls the browser Amazon Silk as it is the connection between Kindle Fire and Amazon's EC2 servers.
Manage research, learning and skills at defaultLogic. Create an account using LinkedIn or facebook to manage and organize your Digital Marketing and Technology knowledge. defaultLogic works like a shopping cart for information -- helping you to save, discuss and share.