...

Let Users Upload From Google Drive and 17 More Sources

One file picker API, one key. The Picker carries every cloud source behind Filestack’s own verified OAuth integrations.

Eighteen sources, each enabled by name in one fromSources array.

The Picker, filestack-js v4, with every source enabled.

Trusted by teams at
SendGrid logo with stylized gray text and overlapping square shapes on the left.
LinkedIn logo followed by the word SlideShare in gray text on a light background.
The word teachable is written in all lowercase, sans-serif letters with a colon between teach and able, in a light purple color on a light background.
A gray Airtable logo featuring a geometric cube design to the left of the word Airtable in bold, modern font.

What building this in-house costs

Building it yourself means the Google Picker API for Drive, the Dropbox Chooser, the OneDrive file picker, and the Box file picker, each with its own SDK and its own OAuth application.

  DIY, per source With Filestack
OAuth app + consent screen File and maintain per provider None
Security certification (Google CASA) Annual paid third-party audit Covered
Production approval reviews Per provider (e.g. Dropbox) Covered
Token refresh + quota handling Your on-call Covered
API deprecations Your roadmap Filestack's problem

Google

A Google Drive picker of your own means Google OAuth verification, and restricted scopes trigger the annual, paid third-party Google CASA assessment. Unverified apps hit a warning screen and a user cap.

What DIY costs →

Dropbox

Production approval review before you can exceed development-user limits.

Skip it with the Picker →

Meta / Instagram

App review, business verification, and permissions that get deprecated under you.

Skip it with the Picker →

The user experience

Users browse folders, search, and multi-select inside their own cloud account, in your app. The file itself moves server to server.

01
Source
Drive, Dropbox…
02
Process
Transform, moderate
03
Deliver
Optimized via CDN

And then the file is in your pipeline

A file picked through the Google Drive file picker behaves like any other upload. Process it, moderate it, transform it, deliver it, all on the same handle. Filestack maintains the Google Drive integration API behind it.

Choose exactly the sources you want

One array controls which sources appear and in what order, so users see the two they actually use rather than all eighteen.

Picker configuration
const client = filestack.init('YOUR_API_KEY');

client.picker({
  fromSources: [
    'local_file_system',
    'googledrive',
    'dropbox',
    'onedrive',
    'box',
    'webcam',
    'url'
  ]
}).open();

Frequently Asked Questions

How do I let users upload from Google Drive?

Enable Google Drive as a source in the Filestack Picker’s fromSources configuration. Filestack provides the verified integration and runs the OAuth flow, so the Google OAuth application and the consent screen are Filestack’s rather than yours.

Do I need Google verification or CASA if I use Filestack?

When users upload through the Filestack Picker, the cloud-provider OAuth integration is Filestack’s, so you are not the app requesting restricted scopes, do not go through Google OAuth verification, and do not commission your own Google CASA assessment for that flow. Always confirm your specific compliance obligations against the provider’s current program documentation.

Which cloud sources does the Filestack Picker support?

The Picker ships 18 sources: My Device, Google Drive, Dropbox, OneDrive, OneDrive Business, Box, Cloud Drive, Custom Source, Gmail, Facebook, Instagram, GitHub, Unsplash, Web Search, Link (URL), Take Photo, Record Video, and Record Audio.

Can I limit which sources appear?

Yes. The fromSources option controls exactly which sources appear in the Picker and in what order, so you can show only the ones your users need.