GitDrop
New

Git release hosting

Host EXE installers, APKs, and release files beside your source code

GitDrop keeps release downloads, version notes, and the repository snapshot in one dependable link. Publish executables, installers, archives, or checksum files without sending recipients through a separate file-sharing page.

Create a repository See private sharing

A simple Git release hosting workflow

Releases live inside the repository page, so visitors can inspect the project before downloading a build and return to the same link for future versions.

  1. 01

    Create the repository page

    Upload the source snapshot first. The same page becomes the stable home for its versioned releases.

  2. 02

    Publish a named release

    Use the owner edit password to add a version, release notes, and downloadable files up to 100 MB each.

  3. 03

    Share one download destination

    Visitors can read the context and download the correct asset from the Releases tab after any required access check.

Code and builds together

Give every download the context it needs

A raw file link says very little. A GitDrop release can show the version, written notes, available assets, and the repository that produced them. That makes it easier for clients and testers to choose the right file and understand what changed.

Installers and archives

Publish EXE installers, APKs, libraries, packaged applications, ZIP archives, and other build artifacts as release assets.

Version notes

Explain what changed, what to install, and any upgrade steps before a visitor downloads the build.

Checksums beside downloads

Include checksum files or values in the release notes so recipients can verify the file they received.

Owner-controlled publishing

Only someone with the repository edit password can create releases or upload new assets.

Better release pages

Make downloads easy to trust

  • Use a clear version such as v1.4.0 and describe the important changes.
  • Name assets by platform and architecture so visitors can choose correctly.
  • Publish a cryptographic checksum and, when possible, sign executable installers.
  • Treat every uploaded binary as untrusted until it has been scanned and verified.

Downloads stay behind repository access

When a repository has a visitor password, its releases use the same access check. GitDrop serves release assets as downloads and never executes them in the browser. The owner edit password remains separate from the visitor credential.

Read the release safety guidance

Release hosting does not replace code signing or malware scanning

Release files are supplied by repository owners. GitDrop does not certify that a binary is safe. Publishers should sign builds and provide checksums; recipients should verify the publisher and scan executable files before running them.