How to block file uploads to ChatGPT: 3 methods compared

Last reviewed: 28 September 2026

This guide explains good practice and vendor features as documented on 28 September 2026. It is not legal advice, and vendor features change; check the linked documentation before you deploy.

Why block file uploads rather than ChatGPT itself?

Files carry far more data than a typed prompt: one spreadsheet can hold a whole customer list. Blocking uploads, or only uploads with sensitive content, removes the biggest leak while keeping the productivity people get from ChatGPT.

Blocking ChatGPT outright tends to move use to personal accounts and phones, where you have no control at all. A narrower rule, "use the company workspace, but no confidential files", is easier to defend to staff and easier to enforce.

Can ChatGPT's own admin settings block file uploads?

Not as a simple switch, as far as OpenAI documents it. We found no workspace setting that turns off file uploads for users in OpenAI's ChatGPT Enterprise workspace settings or role-based access articles, checked on 28 September 2026.

What the workspace does give you is still useful:

• Company data terms. OpenAI states it does not train on Business or Enterprise workspace data by default, and admins control retention on Enterprise and Business.
• Workspace-only access (Enterprise). OpenAI's corporate network controls let your proxy insert a ChatGPT-Allowed-Workspace-Id header so that personal accounts do not work on managed traffic. This closes the route around your controls; it does not inspect files.
• Records (Enterprise). The Compliance Platform lets workspace owners export uploaded files and conversations, which helps investigate an incident after the fact.

So the workspace sets the terms for files that do get uploaded. To stop the upload itself, you need one of the three methods below.

Method 1: How do you block uploads with a browser DLP rule?

Add a data loss prevention rule in the browser that cancels the upload before the file leaves the device. This is the most precise method and needs no TLS inspection, but it only works in the browsers you manage.

Option A: Microsoft Purview DLP in Edge for Business

Microsoft documents this for Intune-managed Windows devices:

1. 1In the Microsoft Purview portal, go to Data loss prevention > Policies > Create policy, and choose Inline web traffic with a custom policy.
2. 2Under adaptive app scopes, select All unmanaged AI apps.
3. 3Choose to enforce the policy in Microsoft Edge for Business.
4. 4Add a rule with the condition Content contains and the sensitive information types you care about, such as credit card numbers or your own custom types.
5. 5Add the action Restrict browser and network activities and set File uploaded to or shared with cloud or AI app to Block. You can also block Text sent to or shared with cloud or AI apps.
6. 6Run the policy in simulation mode first, review matches, then turn it on.

Limits Microsoft states: the policy applies on managed Windows devices, and not all AI apps are supported. When the policy blocks, users are also blocked from opening Firefox and other browsers, and Chrome without the Purview extension, so they cannot simply switch browser. Edge DLP for unmanaged apps is billed pay-as-you-go. Broader Purview Endpoint DLP, which also covers USB and printing, needs Microsoft 365 E5 or an equivalent licence and onboarded devices.

Option B: Chrome Enterprise Premium DLP rules

Google documents this for managed Chrome browsers on Windows, Mac, Linux and ChromeOS:

1. 1Buy the Chrome Enterprise Premium add-on and set up the Chrome Enterprise connector policies.
2. 2In the Google Admin console, go to Security > Access and data control > Data protection and create a rule.
3. 3Set the trigger to File uploaded.
4. 4Add a condition on the URL (for example chatgpt.com) or a URL category, and optionally on file type, file size or content.
5. 5Set the action to Block, and write a custom message of up to 300 characters that tells the employee what to do instead.
6. 6Set the connector's Delay file upload setting so the upload waits for the verdict; otherwise the file may go through before the scan finishes.

Limits Google states: content scanning reads up to 10 MB of text per file. Connector analysis sends content to Google Cloud for scanning, which is a data protection point to assess in its own right.

Option C: A lightweight browser extension (for example VAHTOR)

Smaller teams without Microsoft 365 E5 or Chrome Enterprise Premium can use a browser extension built for AI tools. VAHTOR's Files rule cancels PDF, spreadsheet and office attachments to covered AI sites in the tab; a banner tells the employee why, and an alert is logged without the file contents. It needs no proxy, root certificate or HTTPS decryption and works off VPN. The limits: Chrome and Edge only, on devices with the extension. Desktop AI apps, mobile devices and other browsers are out of reach. DLP rules are in the Business plan (EUR 499 per month + VAT, up to 100 employees).

Method 2: How do you block uploads with a secure web gateway or SSE?

Route web traffic through a secure web gateway or security service edge (SSE) that decrypts TLS, inspects uploads to AI domains and blocks those that break policy. It covers every browser and many desktop apps on managed traffic, at the cost of certificate management.

Microsoft's documented example combines Purview with Microsoft Entra Global Secure Access, or with a supported third-party SASE or secure browser:

1. 1Connect the network layer: for Global Secure Access, the device must be Microsoft Entra joined, with a TLS inspection policy and a content policy in Entra Internet Access. For a third-party SASE, complete its Purview integration and set up pay-as-you-go billing.
2. 2In Purview, create a DLP policy for unmanaged AI apps and set Network and non-Microsoft secure browsers to On under enforcement locations.
3. 3Add the action Restrict browser and network activities and block file uploads, text, or both.
4. 4Test with a pilot group before a wider rollout; some of these features are in preview.

Other gateways follow the same pattern: decrypt, identify the AI app and the upload action, then block. Check your vendor's own documentation for its controls.

Limits: TLS inspection means deploying and trusting a root certificate on every device. OpenAI notes that the ChatGPT desktop and mobile apps use certificate pinning, so your certificate must be added through device management or those apps will fail. Traffic that bypasses the gateway, such as a personal phone on mobile data, is not covered. Microsoft says network data security also covers local AI apps and add-ins, which browser rules do not.

Method 3: How do you block uploads with a CASB session policy?

Put the company ChatGPT workspace behind a cloud access security broker (CASB) session proxy, then add a session policy that inspects and blocks uploads. It governs the company workspace session well and does nothing for personal accounts.

Using Microsoft Defender for Cloud Apps as the documented example:

1. 1Confirm licences: Defender for Cloud Apps and Microsoft Entra ID P1.
2. 2Make sure your ChatGPT workspace signs in through Microsoft Entra ID with SAML SSO (available on ChatGPT Business and Enterprise), and onboard it to Conditional Access App Control.
3. 3Create a Conditional Access policy that routes ChatGPT sessions through app control.
4. 4In the Microsoft Defender portal, go to Cloud Apps > Policies > Policy management > Create policy > Session policy.
5. 5Choose the session control type Control file upload (with inspection), add filters for sensitive content, set the action to Block and customise the message users see.
6. 6Test from a pilot account and review the policy report.

Limits: it only sees sessions that sign in through your identity provider, so personal ChatGPT accounts are untouched unless you also restrict them at the network (see the workspace header above). Session proxies can also affect how some app features behave, so test before rollout.

Which method should you choose?

Pick by the devices and apps you need to cover and the licences you already own. Many companies combine a browser rule for precision with a gateway or workspace restriction to close the routes around it.

What does the employee see when an upload is blocked?

A clear message, if you write one. Chrome Enterprise Premium allows a custom block message of up to 300 characters, Defender for Cloud Apps lets you customise the block message, and VAHTOR shows a banner explaining the rule.

Use the message to point to the allowed route, for example: "Files with customer data can't be uploaded to AI tools. Use the company workspace for public documents, or ask IT." Without that, people assume ChatGPT is broken and look for a workaround.

What are the most common mistakes?

Most problems come from blocking without explaining, or from covering only one route.

• Blocking every file type. Consider blocking only sensitive content, or only uploads to unapproved tools, so public documents still work.
• No message to the user. Silent failures look like a bug and lead to personal devices.
• Skipping simulation mode. Run DLP policies in audit or simulation mode first to see the false positives.
• Ignoring the desktop app. Browser rules do not see the ChatGPT desktop app; either manage it or cover it at the network.
• Forgetting personal accounts. A CASB session policy protects the company workspace only.
• No policy behind the control. Put the upload rule in your AI policy and record who accepted it.

Checklist

• Decide which files are banned from AI tools (all files, or only sensitive content)
• Choose the method(s) based on devices, browsers and licences you already own
• Write the employee-facing block message with the allowed alternative
• Pilot in simulation or audit mode; review false positives
• Decide what to do about desktop apps and personal accounts
• Add the upload rule to the AI policy; record acceptance
• Review alerts monthly and adjust