Chrome was assembled from 25 different code libraries from Google and third parties such as Mozilla's Netscape Portable Runtime, Network Security Services, NPAPI, as well as SQLite and a number of other open-source projects. The JavaScript virtual machine was considered a sufficiently important project to be split off (as was Adobe/Mozilla's Tamarin) and handled by a separate team in Denmark coordinated by Lars Bak at Aarhus. According to Google, existing implementations were designed "for small programs, where the performance and interactivity of the system weren't that important," but web applications such as Gmail "are using the web browser to the fullest when it comes to DOM manipulations and JavaScript", and therefore would significantly benefit from a JavaScript engine that could work faster.

Chrome uses the WebKit rendering engine to display web pages, on advice from the Android team. Like most browsers, Chrome was extensively tested internally before release with unit testing, "automated user interface testing of scripted user actions" and fuzz testing, as well as WebKit's layout tests (99% of which Chrome is claimed to have passed). New browser builds are automatically tested against tens of thousands of commonly accessed websites inside the Google index within 20–30 minutes.

Chrome includes Gears, which adds features for web developers typically relating to the building of web applications (including offline support). However, Google is phasing out Gears in favor of HTML5.

In December 2010 Google announced that to make deploying Chrome easier in a business environment they would provide an official Chrome MSI package. The normal downloaded Chrome installer puts the browser in the user's home directory and provides invisible background updates, but the MSI package will allow installation at the system level, providing system administrators control over the update process.