DEV Community: Sanheen Sethi

Google Killed Drive 'Request Files' in 2023 - Here's the Replacement

Sanheen Sethi — Tue, 03 Mar 2026 05:56:09 +0000

Remember when you could just ask someone to upload files directly into your Google Drive folder? Yeah, Google killed that feature in 2023, and honestly, it left a lot of teams hanging.

If you manage an HR department, run a creative agency, or work in any role where you need to collect files from other people, you know the pain. Before the shutdown, "Request Files" was your go-to — dead simple, built right into Drive, no backend needed. Now? You're left scrambling between WeTransfer, email attachments, and complicated form builders that don't even integrate with Drive.

What Google Took Away (And Why It Still Matters)

Google's "Request Files" feature was slapped directly into Google Drive's right-click menu. One click, and you could generate a shareable link that let anyone — with or without a Google account — upload files straight into your Drive folder. No account creation, no login required. Files landed exactly where you wanted them, organized and searchable.

Why'd Google kill it? According to their official statement, they were consolidating file-sharing features into Google Forms. But here's the problem: Google Forms' file upload field is clunky, limited, and designed for surveys — not serious file collection. You can't even download the files directly from Drive after collection.

For agencies and HR teams, this was catastrophic. Losing a tool that "just worked" meant evaluating a dozen new platforms, learning APIs, and often paying for something that used to be free.

Real-World Pain Points (And Who's Hurting)

HR Recruiting: You're hiring and need resumes, portfolios, and references from candidates. Google Forms? Great for surveys. For serious recruitment? You need files organized by candidate name, by department, with timestamps and metadata.

Design Agencies: Your clients need to submit logos, brand guidelines, photos for the next campaign. You've got 15+ active projects, each with 3-5 clients uploading different asset types. You need those files in Drive, automatically organized by client and project.

Event Organizers: Collecting event photos from attendees, vendor assets for an expo, speaker materials for a conference. You need a branded upload page, a custom link you can share on marketing materials, maybe a QR code for events.

The Modern Solution

There are newer tools designed to replace "Request Files" properly. The best ones have these features:

Share a link or QR code — Anyone can upload files without creating an account
Direct Drive integration — Files land in your Drive folder, organized and searchable
White-label branding — Your logo, your colors, not a generic upload page
Custom form fields — Collect name, email, or custom metadata alongside files
Webhooks & automation — Trigger actions in Zapier, n8n, or your own backend
REST API — Full CRUD operations for developers who need programmatic access

This is the replacement Google should've provided: purpose-built for file collection, works with Drive, and doesn't require everyone to learn a new platform.

Why This Matters

Yes, we're mourning a dead Google feature. But the real insight is this: file collection is fundamental, and it shouldn't require complicated infrastructure.

Most organizations just need:

A simple, brandable upload page
Files ending up in a drive they already use
No account signups for people uploading
Optionally, some automation (webhooks, API, form fields)

Try It Yourself

DriveWidget is a free tool built specifically for this. You can create a branded upload page in under a minute, connect your Drive folder, and share a link — no backend code needed, no login required for uploaders.

Free tier: 1 connection, 1 widget, 1,000 uploads/month.

Have you found other good replacements for Google's "Request Files"? Would love to hear what's working for your team.

Building Upload Pages That Actually Convert (Design Principles That Work)

Sanheen Sethi — Thu, 26 Feb 2026 15:54:33 +0000

Building Upload Pages That Actually Convert (Design Principles That Work)

Most upload pages are forgettable. Users land, upload a file, leave. Then what?

Great upload pages make users want to come back.

The Problem: Upload Pages Are Boring

Default file upload page:

Generic gray box
Boring button text
No context
No trust signals
User thinks: "Is this legit?"

That's a conversion killer.

Principle 1: Make Trust Visible

Users need proof that:

Their file is safe
You know what you're doing
This isn't sketchy

What works:

Your logo, not a generic company logo
Client logos (if applicable) - "trusted by 5,000+ teams"
SSL badge (yes, people still notice)
File count in subtle text: "2.4M files uploaded successfully"
Simple privacy statement: "Your files are encrypted and never shared"

Don't overcomplicate. One trust signal is enough.

Principle 2: Crystal Clear Instructions

Users shouldn't have to think.

Bad:
"Please submit your required assets"

Good:
"Upload your project files (logos, mockups, revisions) - we'll organize them automatically"

Tell them:

What files to upload
Why you need them
What happens next

Principle 3: Minimize Friction

Every extra click is lost users.

Friction reducers:

Drag-and-drop (not just "click to upload")
Show file upload progress
Pre-fill known fields (email from their browser)
Skip optional fields
Confirm immediately after upload ("✅ Got it!")

Principle 4: Visual Hierarchy

Make the upload action stand out.

Big, colored button (not gray)
Descriptive button text: "Upload Files" not "Submit"
Empty space around the upload area
High contrast background

Principle 5: Context Fields Build Value

Don't just collect files. Collect context.

Instead of:

File name
Upload date

Ask for:

Project name (or offer dropdown of existing projects)
File type (logo, revision, asset, etc.)
Notes (optional)
Deadline (if relevant)

Why? Because now you have a system, not a pile of files.

Real Example: Design Agency

A design agency's client portal:

Large, centered upload area (white background, blue border)
Form fields:
- Project (dropdown, auto-filled if returning user)
- Asset Type (choices: Logo, Mockup, Photo, Video, Document)
- Notes (optional)
Trust signal: "Last upload: 2 days ago by Sarah" (showing usage)
Button text: "Upload Assets to [Project Name]"
After upload: "✅ Received 3 files"

Conversion: 95% of uploaded files come with complete context.

Without those fields: 30% of uploads have zero context, requiring manual follow-up.

Principle 6: Mobile-First Design

Most users upload from phones.

Stack form fields vertically
Make tap targets large (44px minimum)
Show file preview on upload
Don't require hover states

Principle 7: Feedback at Every Step

Uncertainty kills conversions.

Before upload: "Drag files here or click"
During upload: Progress bar + file names being uploaded
After upload: "✅ 3 files received" + next steps

The Numbers

Upload page with all 7 principles:

Average upload time: 90 seconds
User confidence: 92% say "felt professional"
Completion rate: 98% (vs. 65% on default pages)

Form context completion: 94% (vs. 20% on email/Slack)

Checklist: Does Your Upload Page Convert?

[ ] Your logo visible (not generic branding)
[ ] One clear action: upload
[ ] Drag-and-drop enabled
[ ] Form fields collect useful context
[ ] Mobile responsive
[ ] Progress feedback during upload
[ ] Confirmation message after upload
[ ] One trust signal visible (SSL, count, or client logos)

0-3 checks: Redesign it
4-6 checks: Good start, optimize weak areas
7-8 checks: You'll convert users

Next: Add Webhooks

Once users upload, trigger automations:

Email notification
Slack message
Spreadsheet update
Task creation

Try DriveWidget

Building a conversion-optimized upload page is exactly what DriveWidget helps you do. All 7 principles baked in.

Try DriveWidget free — no credit card needed. Start converting users today.

The Freelancer's Guide to Replacing Email File Management

Sanheen Sethi — Thu, 26 Feb 2026 15:52:47 +0000

The Freelancer's Guide to Replacing Email File Management

As a freelancer, your sanity depends on staying organized. But email file management will drive you crazy.

The Freelancer Problem

You're juggling:

Client A sends mockups at 2am in a 5-deep email thread
Client B wants feedback on drafts (v1, v2, v2-final, v2-ACTUALLY-final)
Client C is asking "did you get my file?" for the 3rd time
Your hard drive is named "Freelance Work", "Freelance-Final", "Freelance-OLD-DO-NOT-USE"

Meanwhile, that one client from 2022 might send something, and you've got no idea where to put it.

Why Email Sucks for Freelancers

It's invisible to clients
They think you're ignoring them. They resend. You get duplicates. Nobody knows what version is current.

You can't scale systems
With 1 client, email works. With 3 clients, it's chaos. With 5 clients, you're losing work.

Feedback loops break
Client sends file → You download → You move to folder → You open → You edit → You upload somewhere → You send link → They can't find it → They ask again

That's 7 steps for 1 file.

The Freelancer's Solution: Per-Client Upload Pages

Create ONE upload page per client. Give it a name: "Sarah's Project Portal", "Design Review", "Content Submissions"

Client sees:

One branded page with YOUR logo
Clear instructions: "Upload your files here"
Form field for file type (mockups, feedback, revision, final)
That's it

You see:

Everything organized by client
Auto-timestamped versions (no confusion)
Email notification when they upload
Clear workflow: upload → you review → done

Time saved:

45 minutes/day looking for files → 5 minutes/day
That's 40 minutes × 5 days = 3.3 hours/week
At $75/hour = $250/week recovered
$13,000/year of recovered billable time

Real Example: Web Designer with 4 Clients

Marcus used to spend 12 hours/week on file management:

2 hours/week finding files
3 hours/week organizing
4 hours/week fixing version confusion
3 hours/week re-explaining to clients where to send files

With upload pages per client:

Files auto-arrive in right folder
Timestamps handle versioning
Clients know exactly where to submit
Marcus is now billing 12 more hours/week

That's an extra $900/week if he raises rates even slightly.

How to Set It Up (5 Minutes)

Create a folder per client in Google Drive
Create an upload page pointing to that folder
Add a form field for file type/description
Enable auto-naming with date + client name
Send the link to the client

Done. Never think about it again.

What About Legal Stuff?

Contracts should reference "file submission portal" instead of email.

One line: "Client agrees to submit all project files via the shared upload portal. Files are automatically time-stamped and backed up."

That's it. More professional than email anyway.

The Numbers

Freelancers earning $50-100/hour lose $5,000-$20,000/year to disorganization.

An upload page costs $7/month. Over a year: $84.

ROI: If it saves you just 1 hour/week, you're profitable in week 2.

Getting Started

Start with your biggest client. Give them a branded upload page this week. Watch your sanity improve immediately.

Try DriveWidget

This is exactly what DriveWidget was built for. Freelancers managing multiple clients need a system that scales.

Try DriveWidget free — no credit card needed. Scale your freelance business without hiring a VA.

Why Upload Forms Need Webhooks (And What You Can Do With Them)

Sanheen Sethi — Thu, 26 Feb 2026 15:48:57 +0000

Why Upload Forms Need Webhooks (And What You Can Do With Them)

Webhooks transform your upload form from a dumb storage tool into an automation engine.

What Are Webhooks?

Webhooks are HTTP requests that fire when events happen. When someone uploads a file, your app gets notified instantly. You can then trigger automations, send notifications, or update your database.

Real Workflow: Client File Upload = Instant Task Creation

Client uploads design file to your widget
Webhook sends to Zapier
Zapier creates task in Asana
Task assigned to designer
Everything connected, zero manual work

Practical Webhook Examples

Send Slack notification: "New logo from Acme Corp uploaded"
Create Google Sheets row with file metadata
Trigger email notification to team
Call your custom API endpoint
Archive file to AWS S3
Run ML image recognition
Update project status in Airtable

The Power Move: Upload Page + Webhooks

Without webhooks: Upload page is just dumb storage. Files land in Drive, someone has to do something with them.

With webhooks: Upload page becomes workflow trigger. Files land in Drive AND automatically trigger everything downstream.

Real Use Case: Agency Workflow

Design agency gets client assets via DriveWidget. Webhook fires, creates task, notifies team on Slack, updates project status. Files organized automatically. Team gets notified. No manual work.

Time saved per file: 5 minutes. With 20 clients submitting files daily, thats 100 minutes/day.

Getting Started with Webhooks

Most upload platforms include webhook support. DriveWidget includes webhooks at all pricing tiers. Connect via Zapier for no-code automation.

Your New Workflow

Files flow in via your widget
Webhooks fire automatically
Your systems respond (Zapier, n8n, custom API)
Zero manual intervention needed

That's automation that actually works.

Try DriveWidget free at https://drivewidget.com — webhooks included.

Stop Losing Files in Email: 4 Reasons to Use Upload Pages Instead

Sanheen Sethi — Thu, 26 Feb 2026 15:46:46 +0000

Stop Losing Files in Email: 4 Reasons to Use Upload Pages Instead

Email is terrible for collecting files. Your team probably doesn't realize how much time this wastes.

Problem 1: Size Limits Kill You

Gmail caps at 25MB. Outlook at 20MB. Client wants to send a 300MB video. Now they're trying WeTransfer which expires after a week. Then they ask "did you get my file?"

With an upload page: No limits. Files arrive instantly.

Problem 2: Lost in Threads

Emails pile up. Someone sends a file Tuesday, another Friday in same thread. Context is lost.

With form fields: All context attached automatically. Project name, deadline, asset type - everything organized.

Problem 3: No Version Control

Client sends logo.pdf, logo-final.pdf, logo-final-FINAL.pdf. No idea which to use.

With auto-naming: Clear, timestamped versions. No confusion.

Problem 4: You're a Bottleneck

Client has a file. Instead of sharing directly, they email you. You download, upload to Drive, move to folder, send confirmation. 5 unnecessary steps.

With upload page: One step. File is already organized.

The Numbers

Average office worker spends 30 minutes/day on email file management. That's 2.5 hours/week, 120 hours/year per person.

Team of 5: 600 hours/year wasted.

Real Workflow: Freelancer Gets 50% Time Back

Maya spends 45 minutes/day finding files. With upload page: automatically organized, 45 minutes back daily.

At $80/hr: $9,360/year recovered.

Try It Free

Most platforms offer free tier. See how much faster it is. You'll never go back to email.

Try DriveWidget

This is exactly what DriveWidget solves. Create a branded upload page in minutes—no backend, no hassle.

Try DriveWidget free — no credit card needed. Stop losing files in email today.

How to Build a Client Portal Without Code in 2026

Sanheen Sethi — Thu, 26 Feb 2026 15:17:55 +0000

How to Build a Client Portal Without Code in 2026

Agencies and service businesses spend way too much time juggling file collection. Here's how to build a professional client portal in 5 minutes—without any coding.

The Current Mess

Most teams are still doing this:

Shared Google Drive folders (clients see everything)
Email attachments (size limits, clutter)
Slack/WhatsApp (unprofessional, files disappear)
Combining 3-4 different tools (forms + storage + notifications)

It's fragmented, slow, and unprofessional.

What You Actually Need

A proper client portal needs:

One branded upload page (your branding, not generic)
Form fields to collect context (client name, project, deadline)
Automatic organization (files auto-sort by project or type)
Instant notifications (you know when files arrive)
An audit trail (who uploaded what, when)

Step-by-Step Setup (Literally 5 Minutes)

1. Create your folder structure

Projects/
├── Acme Corp/
├── TechStart/
└── DesignCo/

2. Create an upload page
Just give it a name: "Acme Corp Assets"

3. Add smart form fields

Project Name (dropdown)
Asset Type (dropdown: Logo, Photo, Video, Document)
Deadline (date picker)
Notes (optional)

4. Enable auto-folders
File auto-organizes: /Acme Corp/Photos/2026-02/
No manual organizing needed.

5. Share the link
Send clients their unique URL. They bookmark it.

Real Example: Design Agency

Sarah's agency collects assets from 12 clients monthly. Before: 2 hours/week organizing. After: total setup 5 minutes, 2 hours/week saved.

Each client gets a branded upload page, files auto-organize automatically, and everyone saves time.

Why This Beats Building It Yourself

Building a custom client portal is a classic rabbit hole:

Need a backend developer ($100/hr+)
Need file storage (AWS S3, etc. = ongoing cost + management)
Need to handle security yourself (nightmare)
Need to maintain it forever
Need to add features later (email notifications, webhooks, etc.)

Cost: $5,000 - $20,000 to build + $200-500/month to run

Alternative: Pre-built solution, $0-7/month, zero maintenance

The math is obvious.

Why Google Drive?

Google Drive is already:

Free (everyone has it)
Unlimited storage for $20/mo
Easy to share
Works offline
Backed up automatically
Professional (clients trust it)

So why re-invent? Just add an upload interface on top.

The Secret: Webhooks

When a file arrives, you can:

Send a Slack notification
Create a task in your project manager
Update a spreadsheet
Trigger any automation
Call your custom code

So the "client portal" becomes a trigger for your entire workflow.

Getting Started

Most platforms have a free tier that lets you:

1 upload page
300-1000 uploads/month
1 Google Drive folder

Perfect for testing before committing.

Start free, upgrade only if you need it.

Try DriveWidget

This is exactly what DriveWidget does. Instead of managing folders and files manually, DriveWidget creates a branded upload page that collects files directly into your Google Drive.

Try DriveWidget free — no credit card needed. Collect files from clients into your Google Drive instantly.

How to Collect Files into Google Drive — No Google Login Required for Uploaders

Sanheen Sethi — Sun, 22 Feb 2026 22:03:27 +0000

If you've ever tried to collect files from clients, students, or collaborators using Google Drive, you've probably hit one of these walls:

Google Forms requires uploaders to have a Google account (the #1 complaint worldwide)
Google's "Request Files" feature was quietly killed in 2023
Shared folders are messy and hard to manage
Email attachments max out at 25MB and scatter files everywhere

I ran into this problem while building tools for agencies and freelancers. They needed a simple way to say: "Upload your files here, they'll land in my Google Drive." No login required for the person uploading.

So I built DriveWidget — and I want to share how it works and how you can set it up in under 2 minutes.

The 3 Ways to Collect Files

1. Embeddable Upload Widget

Drop one line of HTML into any website:

<iframe
  src="https://drivewidget.com/widget/YOUR_WIDGET_ID/embed"
  width="100%"
  height="400"
  frameborder="0"
></iframe>

Works with WordPress, Squarespace, Wix, Webflow, React, Next.js — anything that supports HTML.

2. Standalone Upload Page

Every widget gets a shareable link like:

https://drivewidget.com/u/your-custom-slug

Share it via email, Slack, or even a QR code. No account needed for uploaders.

3. REST API

For developers who want programmatic control:

# Upload a file via API
curl -X POST https://drivewidget.com/api/upload/WIDGET_ID \
  -H "X-API-Key: your_key" \
  -F "file=@document.pdf" \
  -F "full_name=John Doe" \
  -F "email=john@example.com"

The API also supports listing files, downloading, and deleting — full CRUD on your Google Drive folder.

How It Works Under the Hood

You connect your Google Drive via OAuth (standard Google consent screen)
You create a widget — pick colors, set allowed file types, add form fields
Uploaders visit the page or widget — they drag & drop files
Files land directly in YOUR Google Drive folder — organized by date or form field values

The key insight: uploaders never interact with Google at all. They see your branded upload page, not a Google login screen.

Features That Save Time

Feature	What it does
Form fields	Collect name, email, or custom data alongside files
Auto-folders	Organize uploads into subfolders by date or field value
File renaming	Auto-rename files with patterns like `{date}_{name}_{original}`
Webhooks	Trigger Zapier/Make/custom workflows on each upload
Email alerts	Get notified when someone uploads
Password protection	Lock upload pages behind a password
Custom CSS	Full styling control on Pro plan

Use Cases I've Seen

Agencies collecting assets from multiple clients (one upload page per client)
HR teams collecting resumes into organized Drive folders
Teachers receiving homework without requiring student Google accounts
Event organizers collecting photos via QR code upload links
Freelancers with branded upload portals for clients

Quick Comparison

	Google Forms	DriveWidget
Uploader needs Google account	Yes	No
REST API	Limited	Full CRUD
Custom branding	No	Yes
Webhooks	No	Yes
Auto-organize files	No	Yes
Embed on any site	No	Yes

Getting Started

Sign up at drivewidget.com (free tier: 3 connections, 5K requests/month)
Connect your Google Drive via OAuth
Create your first widget
Embed it or share the upload link

The free tier is genuinely usable — no credit card required, no expiration.

I built this as a solo developer with FastAPI + Next.js + PostgreSQL, running on a $7/mo VPS. Happy to answer any questions about the technical architecture or use cases.

What's your current workflow for collecting files from people who don't have Google accounts?