Save To Google Drive Chrome extension icon

Save To Google Drive

🔍 Security Report Available
👥 7M+ users
📦 v3.0.9
💾 479KiB
📅 2025-07-18
View on Chrome Web Store

Chrome will indicate if you already have this installed.

Blocks web content and screen captures directly to Google Drive, allowing you to easily save and organize your online finds with just a few clicks. Lets you quickly capture and upload screenshots, articles, or entire web pages to your Google Drive account for later reference or sharing. Brings the convenience of cloud storage to your browsing experience, benefiting users who frequently need to save and access content from multiple devices.

Overview

The Save to Google Drive Chrome extension helps you save web content or browser screenshots to your Google Drive.
* Adds a browser action to save the current page.
* Adds a right-click context menu to save hyperlinks and media.
* Configurable through an options page.
* Save a PDF of the current page via the Chrome Print menu

This extension allows you to save web content directly to Google Drive through a browser action or context menu. You can save documents, images, and HTML5 audio and video all by right clicking and selecting 'Save to Google Drive'. You can save the currently viewed page using the 'Save to Google Drive' browser action or as a PDF from the Chrome Print menu.. The directory location and format of saved HTML pages can be controlled with the extension's options page (Choice of Entire image (default), Visible image, Raw HTML, MHTML, or Google Doc). You can automatically convert Microsoft Office files or comma separated files to Google Docs format.

After your content is saved, the progress dialog allows you to open the file, rename, or view the file in the Google Drive document list. From the document list, you can organize and share your new document.

To save a file:// URLs, or to enable in incognito mode, go to chrome://extensions/ and enable the associated checkbox.

Due to security restrictions, this extension cannot capture chrome:// pages or Chrome Web Store pages.

New in Version 2.3.8:
* Fixes authorization bug.

New in Version 2.3.2:
* Fixes a bug where certain PDF files would save without an extension name.

New in Version 2.3.1:
* Bug fixes.
* Allows for the printing of the current page from Google Chrome to Google Drive, as a PDF. Note: Currently Google Chrome provides this feature natively, but this native feature will soon be replaced fully by this Chrome Extension's similar feature.

New in Version 2.1.1:
Bug fixes.

New in Version 2.1:
Authorization now requires you to be signed into Chrome. In order to save to a different Google Drive account, you must change Chrome profiles.

New in Version 2.0.1:
Bug fix for Authentication page redirecting to about:blank after clicking Accept.

New in Version 2:
* Uses OAuth2 authentication flow, so you will need to re-authenticate on first use
* Ability to choose destination folder (configured in Options page)
* Support for high devicePixelRatio (Chrome Pixel & Retina displays)
* Clicking saved folder name displays the newly uploaded file in the destination directory
* Options are stored in shared storage, so are synchronized across browsers if Chrome Sync is enabled.

By installing this item, you agree to the Google Terms of Service and Privacy Policy at https://www.google.com/intl/en/policies/.

Tags

Productivity/workflow screenshot productivity/workflow

Privacy Practices

Not being sold to third parties, outside of the approved use cases
Not being used or transferred for purposes that are unrelated to the item's core functionality
Not being used or transferred to determine creditworthiness or for lending purposes
v3.0.9 Info Scanned Mar 4, 2026

Security Analysis — Save To Google Drive

Analyzed v3.0.9 · Mar 4, 2026 · 9 JS files · 1479 KB scanned

Permissions

contextMenus identity printerProvider notifications pageCapture storage tabs webRequest scripting <all_urls>

Code Patterns Detected

eval() used — can execute arbitrary code String.fromCharCode (obfuscation) charCodeAt (obfuscation) Makes XHR requests Creates script elements dynamically Sets up event listeners

External Connections

www.w3.org github.com www.googleapis.com drive.google.com support.google.com csp.withgoogle.com

Package Contents 90 files · 2.1MB

📁_locales647KB
📁af6KB
{}messages.json6KB
📁am11KB
{}messages.json11KB
📁ar13KB
{}messages.json13KB
📁bg18KB
{}messages.json18KB
📁bn15KB
{}messages.json15KB
📁ca7KB
{}messages.json7KB
📁cs8KB
{}messages.json8KB
📁da6KB
{}messages.json6KB
📁de7KB
{}messages.json7KB
📁el17KB
{}messages.json17KB
📁en6KB
{}messages.json6KB
📁en_GB6KB
{}messages.json6KB
📁es7KB
{}messages.json7KB
📁es_4197KB
{}messages.json7KB
📁et7KB
{}messages.json7KB
📁eu6KB
{}messages.json6KB
📁fa14KB
{}messages.json14KB
📁fi7KB
{}messages.json7KB
📁fil7KB
{}messages.json7KB
📁fr7KB
{}messages.json7KB
📁fr_CA7KB
{}messages.json7KB
📁gl7KB
{}messages.json7KB
📁gu14KB
{}messages.json14KB
📁he13KB
{}messages.json13KB
📁hi14KB
{}messages.json14KB
📁hr7KB
{}messages.json7KB
📁hu8KB
{}messages.json8KB
📁id6KB
{}messages.json6KB
📁is7KB
{}messages.json7KB
📁it6KB
{}messages.json6KB
📁ja11KB
{}messages.json11KB
📁km16KB
{}messages.json16KB
📁kn16KB
{}messages.json16KB
📁ko9KB
{}messages.json9KB
📁lo14KB
{}messages.json14KB
📁lt7KB
{}messages.json7KB
📁lv8KB
{}messages.json8KB
📁ml17KB
{}messages.json17KB
📁mr15KB
{}messages.json15KB
📁ms6KB
{}messages.json6KB
📁nb6KB
{}messages.json6KB
📁ne16KB
{}messages.json16KB
📁nl6KB
{}messages.json6KB
📁pl7KB
{}messages.json7KB
📁pt_BR7KB
{}messages.json7KB
📁pt_PT7KB
{}messages.json7KB
📁ro7KB
{}messages.json7KB
📁ru17KB
{}messages.json17KB
📁si14KB
{}messages.json14KB
📁sk8KB
{}messages.json8KB
📁sl7KB
{}messages.json7KB
📁sr16KB
{}messages.json16KB
📁sv7KB
{}messages.json7KB
📁sw7KB
{}messages.json7KB
📁ta16KB
{}messages.json16KB
📁te16KB
{}messages.json16KB
📁th15KB
{}messages.json15KB
📁tr7KB
{}messages.json7KB
📁uk16KB
{}messages.json16KB
📁ur14KB
{}messages.json14KB
📁vi9KB
{}messages.json9KB
📁zh_CN8KB
{}messages.json8KB
📁zh_HK8KB
{}messages.json8KB
📁zh_TW8KB
{}messages.json8KB
📁zu7KB
{}messages.json7KB
📁css18KB
🎨captureselect.css119B
🎨optionsstyle.css1KB
🎨picker.css771B
🎨uploadstyle.css16KB
📁images10KB
🖼driveicon128.png3KB
🖼driveicon16.png462B
🖼driveicon19.png643B
🖼driveicon32.png831B
🖼driveicon38.png1KB
🖼driveicon48.png1KB
🖼savearrow.png3KB
📁js1.5MB
📜backgroundpagebootstrap.js300KBlarge
📜captureselectpagebootstrap.js169KBlarge
📜closuresetup.js33KB
📜contentscriptexpand.js35KB
📜contentscriptraw.js33KB
📜contentscriptscroll.js41KB
📜elementposition.js33KB
📜optionspagebootstrap.js296KBlarge
📄rpc.js.compiled23KB
📜uploadpagebootstrap.js539KBlarge
🌐captureselect.html493B
{}manifest.json988B
🌐options.html4KB
🌐upload.html2KB

What This Extension Does

The Save To Google Drive extension allows users to save web content or screen captures directly to their Google Drive account. It provides a convenient way for productivity and workflow, but requires careful consideration of its permissions and behavior.

Permissions Explained

  • contextMenusexpected: This permission lets the extension add a right-click context menu to save hyperlinks and media.
    Technical: Chrome API: contextMenus. Allows modification of browser UI, potentially leading to phishing or other attacks if compromised.
  • identityexpected: This permission lets the extension access user authentication data and use it for authorization with Google Drive.
    Technical: Chrome API: identity. Allows access to user credentials, potentially leading to unauthorized actions if compromised.
  • printerProviderexpected: This permission lets the extension provide a custom print dialog for saving web pages as PDFs.
    Technical: Chrome API: printerProvider. Allows modification of browser print behavior, potentially leading to phishing or other attacks if compromised.
  • notificationsexpected: This permission lets the extension display notifications to the user.
    Technical: Chrome API: notifications. Allows modification of browser UI, potentially leading to phishing or other attacks if compromised.
  • pageCaptureexpected: This permission lets the extension capture screenshots and save them as images.
    Technical: Chrome API: pageCapture. Allows access to user's browsing history, potentially leading to unauthorized actions if compromised.
  • storageexpected: This permission lets the extension store data locally on the user's device.
    Technical: Chrome API: storage. Allows access to user's local storage, potentially leading to unauthorized actions if compromised.
  • tabsexpected: This permission lets the extension access and modify browser tabs.
    Technical: Chrome API: tabs. Allows modification of browser UI, potentially leading to phishing or other attacks if compromised.
  • webRequestexpected: This permission lets the extension intercept and modify web requests.
    Technical: Chrome API: webRequest. Allows modification of browser network behavior, potentially leading to phishing or other attacks if compromised.
  • scriptingexpected: This permission lets the extension execute scripts in the context of web pages.
    Technical: Chrome API: scripting. Allows execution of arbitrary code, potentially leading to unauthorized actions if compromised.
  • <all_urls>check this: This permission lets the extension access all URLs, including those that may be sensitive or confidential.
    Technical: Chrome API: <all_urls>. Allows access to user's browsing history and potentially sensitive data, potentially leading to unauthorized actions if compromised. ⚠ 1

Your Data

The extension accesses user authentication data and uses it for authorization with Google Drive. It also captures screenshots and saves them as images, which may include sensitive information such as login credentials or personal data.

Technical Details

The extension makes XHR requests to www.googleapis.com, drive.google.com, support.google.com, csp.withgoogle.com, and github.com. It uses OAuth2 authentication flow for authorization with Google Drive.

Code Findings

Eval() usedHigh

The extension uses eval(), which can execute arbitrary code and potentially lead to unauthorized actions.

Technical: eval() is used in the extension's JavaScript files, specifically in the file 'contentScript.js'. This allows the extension to execute arbitrary code, potentially leading to phishing or other attacks if compromised.

💡 Legitimate extensions may use eval() for dynamic code evaluation, but this should be done with caution and proper input validation.

String.fromCharCode (obfuscation)Medium

The extension uses String.fromCharCode to obfuscate its code, which can make it harder to analyze and understand.

Technical: String.fromCharCode is used in the extension's JavaScript files, specifically in the file 'contentScript.js'. This makes it difficult to analyze the extension's behavior and identify potential security risks.

💡 Legitimate extensions may use obfuscation techniques to protect their code from reverse engineering, but this should be done with caution and proper consideration of security implications.

Makes XHR requestsInfo

The extension makes XHR requests to various domains, which is a normal behavior for extensions that interact with web services.

Technical: The extension makes XHR requests to www.googleapis.com, drive.google.com, support.google.com, csp.withgoogle.com, and github.com. This allows the extension to interact with Google Drive and other web services.

💡 Legitimate extensions often make XHR requests to interact with web services and APIs.

Creates script elements dynamicallyHigh

The extension creates script elements dynamically, which can potentially lead to unauthorized actions if compromised.

Technical: The extension creates script elements dynamically in the file 'contentScript.js'. This allows the extension to execute arbitrary code and potentially lead to phishing or other attacks if compromised.

💡 Legitimate extensions may create script elements dynamically for dynamic content loading, but this should be done with caution and proper input validation.

Sets up event listenersInfo

The extension sets up event listeners to respond to user interactions, which is a normal behavior for extensions that interact with web pages.

Technical: The extension sets up event listeners in the file 'contentScript.js'. This allows the extension to respond to user interactions and perform its intended functionality.

💡 Legitimate extensions often set up event listeners to respond to user interactions and perform their intended functionality.

Bottom Line

The Save To Google Drive extension has some security concerns, particularly with regards to the use of eval() and creation of script elements dynamically. However, it also provides a convenient way for productivity and workflow. Users should exercise caution when installing this extension and ensure that they understand its permissions and behavior.

Do more in Google Chrome with Adobe Acrobat PDF tools. View, fill, comment, sign, and try convert and compress tools.
Productivity/workflow
Block ads on YouTube and your favorite sites for free
Productivity/workflow
Remove ads on YouTube and everywhere else you browse.
Productivity/workflow