You can send images from the web app to a bucket in Google Cloud Storage. The browser sends each image directly to your bucket. For the general steps of an upload, read Uploads: send images to processing and storage services.
You sign in with your Google account. You do not need an access key or a CORS rule on the bucket.
What you need
- A Google account. To learn about Google Cloud Storage, click the icon at the right end of the Google Cloud Storage row in the New Upload dialog. The Google Cloud Storage site opens in a new tab.
- A bucket in Google Cloud Storage.
- Permission for your Google account to add files to the bucket, for example the role Storage Object Creator. To also replace files that are already in the bucket, your account needs a role such as Storage Object User. The owner of the bucket can give you the role.
- A computer browser at app.dronelink.com.
- A plan that includes this integration. To see which plans include it, find "Google Cloud Storage" in the plan comparison table.
Sign in with Google
- Open Uploads and click New Upload.
- Click Google Cloud Storage.
- Click Sign in with Google. A Google window opens.
- Select your Google account, or sign in to it.
- Allow access to Google Cloud Storage.
The Google window closes. The dialog shows "Signed in as" and the email address of your Google account.
The web app uses this access only in your browser. It uses it to read your email address, to check the bucket and to add the images. It does not send the access to Dronelink.
The sign-in stays in this browser tab for about one hour. In this time, a new upload does not need a new sign-in. If you reload the tab, sign in again.
An upload pauses about 55 minutes after the sign-in in the dialog. Read "A long upload: Sign in again" below. Before a long upload, click Sign out and sign in again just before you start the upload.
To use a different Google account, click Sign out. Then click Sign in with Google again. An upload that is active continues with the Google account that started it.
If Google shows a warning about the app
During the sign-in, Google can show a warning page. The page says that Google has not verified the app.
For Dronelink, it is safe to continue. To continue, open the advanced details on the warning page. Then click the link that continues to the app.
Settings
- Bucket: the name of the bucket, for example my-bucket. You can also enter gs://my-bucket.
- Path: optional. The folder in the bucket for the images, for example folder/subfolder. If you do not enter a path, the images go to the top level of the bucket. If you start the upload from a mission page, the default is the mission name and the capture time, for example my-mission/2026-11-16_14-30-00.
Next stays unavailable until you sign in and enter a Bucket.
The browser keeps the Bucket and the Path for the next upload.
When you click Next, the web app makes sure that your Google account can add files to the bucket. If it cannot, the dialog stays at Configure Settings and shows a message, for example:
- "The bucket bucket does not exist, or your Google account cannot see it.": make sure that the bucket name is correct. Then make sure that you signed in with the correct Google account.
- "Your Google account cannot add files to the bucket bucket. Ask the bucket owner for the Storage Object Creator role.": ask the owner of the bucket to give this role to your Google account. Then click Next again.
In the messages, bucket is the name of your bucket. If your Google sign-in expired, the dialog shows "The Google sign-in expired. Sign in again to continue the upload.", and the Sign in with Google button shows again. For these messages, read also "Troubleshooting" below.
Where the images go
Each image goes to the Path in the bucket, with its file name. Example: DJI_0001.JPG becomes folder/subfolder/DJI_0001.JPG. The web app does not keep folders from your computer.
If two or more files in the upload have the same name (capital and small letters count as the same), each file after the first gets a number before the extension. A file name with no extension gets no number. The number is the position of the file among the files that the upload sends. The first file is 0. Files with the label Skipped or Missing do not count. Example: folder/subfolder/DJI_0001_7.JPG.
If a file with the same name is already in the bucket, the result depends on your role:
- With Storage Object User, the new file replaces the file in the bucket.
- With Storage Object Creator, Google refuses the new file, and the upload stops.
To keep each upload apart, use a different Path for each upload.
After the upload
The upload card shows the bucket and the path. To see the images, click Open on the upload card. The folder of the Path opens in the Google Cloud console, in a new tab.
The console shows the images only to a Google account that can list the objects in the bucket, for example with the role Storage Object User. The role Storage Object Creator alone cannot list objects.
A long upload: Sign in again
A Google sign-in in the web app is valid for about one hour from the time you sign in. About 55 minutes after the sign-in, an upload that is not complete waits for a new sign-in:
- The Uploads panel opens.
- The upload card shows "The Google sign-in expired. Sign in again to continue the upload." and a Sign in again button.
- Your other uploads continue.
To continue the upload:
- Click Sign in again. A Google window opens.
- Sign in with the same Google account that started the upload.
The upload then sends the files that did not arrive. A very long upload can wait again about 55 minutes after each Sign in again. Keep the browser tab open while the upload waits. If you close or reload the tab, the upload stops.
Troubleshooting
- "The Google sign-in did not complete. Try again.": the Google window closed before the sign-in was complete, or you did not allow the access. Also, the browser or a browser extension can block the Google sign-in. Click Sign in with Google again, or Sign in again on the upload card. If the browser blocks pop-up windows, allow them for app.dronelink.com. If an extension blocks the Google sign-in, turn it off for app.dronelink.com.
- "Allow access to Google Cloud Storage in the Google sign-in, then try again.": in the Google window, you did not allow access to Google Cloud Storage. Sign in again, and allow this access.
- "The bucket bucket does not exist, or your Google account cannot see it.": make sure that the bucket name is correct, and that you signed in with the correct Google account.
- "Your Google account cannot add files to the bucket bucket. Ask the bucket owner for the Storage Object Creator role.": ask the owner of the bucket to give this role to your Google account.
- "The Google sign-in expired. Sign in again to continue the upload.": on an upload card, click Sign in again. In the New Upload dialog, click Sign in with Google.
- "Sign in again with email, the Google account that started this upload.": you signed in with a different Google account. Click Sign in again, and select the Google account that the message shows.
- "Your Google account cannot add file to the bucket bucket. If a file with that name is already there, replacing it needs the Storage Object User role.": a file with this name is probably already in the bucket. Use a different Path, or ask the owner of the bucket for the role Storage Object User. Then start a new upload.
- "Google Cloud Storage refused file:" and a reason: Google refused the file. The reason comes from Google. Correct the cause, and start a new upload.
- "Error: Upload failed" or "Error: Upload failed with status" and a number: an image did not get to the bucket. The web app sends a failed image again, up to 3 times. If Google refused the image, for example with status 404, the web app does not send it again. If the image does not arrive, the upload stops. Start a new upload.
- One file failed: the upload stops. The files that arrived stay in the bucket.
In the messages, bucket is the name of your bucket, and file is the full name of the file in the bucket, with the Path. email is the email address of the Google account that started the upload.