Set up Google Drive upload

Klikat uploads to your Drive with your credentials — there's no Klikat server in between. That means creating a Google Cloud project once, about ten minutes.

1. Create a project

   console.cloud.google.com › project dropdown › New project. Call it Klikat. Nothing here costs money.

2. Turn on the Drive API

   APIs & Services › Library › search Google Drive API › Enable.

3. Configure the consent screen

   APIs & Services › OAuth consent screen (newer consoles call this Google Auth Platform).

   Field	Value
   User type	External
   App name	Klikat Screen Recorder
   Support & developer email	your email
   App home page	https://klikat.com
   Privacy policy	https://klikat.com/screenrecorder/privacy.html
   Authorized domain	klikat.com
   Scope	https://www.googleapis.com/auth/drive.file

   drive.file is a non-sensitive scope: it only grants access to files the app itself creates, so it needs no Google verification review.

   Set the publishing status to "In production", not Testing. While the consent screen is in Testing, Google expires the refresh token after 7 days, so Klikat would lose access every week. Publishing removes that limit — with only drive.file you can publish straight away. Google asks for the homepage, privacy policy and a domain you've verified in Search Console, which is why those fields are filled in above.

4. Create the OAuth client

   APIs & Services › Credentials › Create credentials › OAuth client ID.

   • Application type: Desktop app — this is the important bit, it enables the loopback sign-in Klikat uses
   • Name it Klikat on Mac
   • Copy the Client ID and Client secret

   A desktop client's "secret" isn't really secret — Google's own documentation says installed apps can't keep one — which is why Klikat asks for yours instead of shipping one. It's stored in your macOS Keychain.

5. Connect Klikat

   Settings › Upload › Google Drive:

   • Paste the Client ID and Client secret
   • Click Connect Google Drive — your browser opens
   • Choose your account and allow access
   • The browser says you can close the tab, and Settings shows the connected account

   Then set the Folder (default Klikat Recordings). Klikat creates it on the first upload. Turn on year/month subfolders for Klikat Recordings › 2026 › 09.

If something goes wrong

• "Google hasn't verified this app" during sign-in: expected for a personal project. Click Advanced › Go to Klikat Screen Recorder. It's your own project granting access to itself.
• Access stops working after about a week: the consent screen is still in Testing. Publish it (step 3), then reconnect once.
• "Couldn't open a local port for sign-in": sign-in runs a tiny web server on 127.0.0.1 to catch Google's redirect. A VPN or security tool intercepting local traffic is the usual cause — turn it off for the sign-in and try again.
• Klikat can't see the rest of your Drive. With drive.file it only touches what it created, which is also why there's no folder browser — it creates folders by name instead.

Still stuck? Email [email protected].