Skip to content
rafatostaPublic

About

Google Drive for Linux

Topics

Resources

Stars

18 stars

Watchers

0 watching

Forks

Latest commit

 

History

1,290 Commits

Folders and files

Repository files navigation

DriveSync

A Google Drive client for Linux.

DriveSync is an early-stage Linux application for connecting Google accounts and editing their local names. Its GTK4/Libadwaita interface follows the GNOME design guidelines; GNOME is not a requirement for using the application. It is a technical preview, not a stable release.

What you can do today

The current application does not synchronize files. The interface currently focuses on account connection and local account names.

Feature Current availability and limits
Google accounts Connect and manage multiple accounts, each with its own settings and credentials.
Account identity Edit and save a local name without changing the Google profile. New accounts open this editor automatically.
Background operation Keep the application running when allowed by the desktop. No synchronization runs in the background.

Download and install the experimental Flatpak

Prebuilt packages are available for x86_64 Linux systems (64-bit Intel/AMD) through Production Flatpak on GitHub Actions. Each successful build from main provides an experimental installer; these packages are not stable releases.

Download

  1. Sign in to GitHub. GitHub requires an account to download workflow artifacts.
  2. Open Production Flatpak and select the newest successful run on main (green check mark).
  3. Scroll to Artifacts and download DriveSync-experimental-x86_64-<commit>.
  4. Extract the downloaded ZIP. It contains the .flatpak installer, a .sha256 checksum, and INSTALL.txt.

The commit identifier in the filename identifies the source used to build the package. Artifacts are retained for 30 days and may expire. If the latest run failed or is still running, use an earlier successful run with an available artifact.

Install and run

Install Flatpak using your Linux distribution's package manager, or follow the Flatpak setup guide. Then add Flathub for the required GNOME runtime:

flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

Open a terminal in the extracted folder, containing only one extracted build. The * in the commands below automatically matches the commit identifier in the filename:

sha256sum -c DriveSync-experimental-x86_64-*.flatpak.sha256
flatpak install --user ./DriveSync-experimental-x86_64-*.flatpak
flatpak run com.rtosta.DriveSync

Continue with installation only if the checksum reports OK. Flatpak may download the required runtime during installation. You can also launch DriveSync from your desktop's application menu.

Connect your Google account, then review and save its local display name. The prebuilt application already includes its OAuth client configuration: you do not need to create a Google Cloud project or provide a JSON file.

Google sign-in status

The production OAuth project accepts external accounts without adding them to a test-user list. Google verification is still pending, so an unverified-app warning and a limit of 100 users currently apply. Institutional Google Workspace accounts may also be restricted by their administrator. Review the permissions before granting access.

Update or uninstall

These standalone bundles do not provide automatic updates. To update, download and extract a newer successful build, verify its checksum, and run the same flatpak install --user ./...flatpak command with the new filename. Accept the update prompt.

To uninstall:

flatpak uninstall --user com.rtosta.DriveSync

To report a problem, include the commit identifier from the installer filename and your Linux distribution and desktop environment. Do not attach OAuth tokens or private files.

Install the local checkout

With the GNOME SDK and Rust extension specified in the selected Flatpak manifest already installed, build and install for the current user:

./scripts/install-user.sh normal
# Or install the development variant:
./scripts/install-user.sh devel

The script uses flatpak-builder or the installed org.flatpak.Builder app. The normal variant requires data/oauth/production.json. Builds use separate directories under _build/; repeating the command updates the selected variant. The normal and development apps use separate application IDs and account storage. Close an existing instance before launching the installed update:

flatpak run com.rtosta.DriveSync
# Development variant:
flatpak run com.rtosta.DriveSync.Devel

What's next

Synchronization will be redesigned separately. Future behavior must preserve the project's safety invariants and be validated before it is exposed.

Support development

DriveSync is free and open source, developed and maintained in my spare time. If you find the project useful, you can support its development using the same donation channels as ZapZap:

Method Link
GitHub Sponsors Sponsor on GitHub
Ko-fi Support on Ko-fi
PayPal Donate with PayPal
Wise Donate with Wise
Pix (Brazil) Donate with Pix

All contributions are voluntary. DriveSync remains free and open source.

License and copyright

Copyright (C) 2026 Rafael Tosta Santos.

DriveSync is free software distributed under the GNU General Public License, version 3.0 only (GPL-3.0-only). You may use, study, modify, and redistribute it under the terms of that license. See the LICENSE file for the full license text.

Feedback

Found a problem or have a suggestion? Open an issue.

DriveSync is an independent project and is not affiliated with Google.

Build identification

About, Welcome, and the account sidebar display the package version and source revision, for example 0.1.0 (a1b2c3d). About's troubleshooting information contains the full revision. Both Flatpak application IDs use the same format. -modified indicates changes to tracked files; untracked and ignored files are not included in this check. The revision identifies source code, not a unique build invocation.

The build detects Git metadata automatically, including the local directory sources copied by the current Flatpak manifests. When packaging sources without Git metadata, set DRIVESYNC_BUILD_REVISION in the build environment to the full commit hash (optionally followed by -modified) before running Cargo. In a Flatpak manifest, set it under the module's build-options.env. Without Git or an explicit revision, the app displays unknown. No Git access is needed at runtime.

About

Google Drive for Linux

Topics

Resources

Stars

18 stars

Watchers

0 watching

Forks

Releases

Sponsor this project

Packages

Contributors

Languages