Postman Scratch Pad Removed: Login Required to Save
Workaround available Windows, macOS, Linux Updated November 13, 2026Based on 5 user reportsHow we research
Quick answer
Postman discontinued the Scratch Pad (gone in v10.18+). Without an account you only get the lightweight API Client with local history. To keep collections you must sign in or move to an offline tool.
Most likely fix: Use the lightweight API Client
How to fix it
Try these in order — the most common fix is first.
1. Use the lightweight API Client
- On launch choose to continue with the lightweight client (or sign out)
- You can send HTTP, WebSocket, GraphQL, gRPC and MQTT requests and view history, stored locally only
Did this fix it?2. Migrate old Scratch Pad data
- If you still have access: Settings > Data tab > Scratch Pad Data > Migrate Data, pick a workspace, Move Data
- If access is lost, Postman prompts you to export individual collections/environments to files; bulk export is not available
Did this fix it?3. Import exported files
- Sign in, open Workspaces, click Import in the sidebar, drag the file and Import
Did this fix it?4. Move to an offline-first tool
- Export collections as JSON and import into Bruno, Insomnia or Hoppscotch if you do not want cloud accounts
Did this fix it?
Symptoms
Postman opens asking you to sign in, collections and environments are missing, or you cannot save requests without an account.
Why it happens
- Scratch Pad deprecated and removed from v10.18 and later
- Lightweight API Client has no collections or environments
- Workspaces need a Postman account
This guide also covers
- postman scratch pad removed
- postman without login
- postman offline mode
- postman forced login
Still not working?
If Postman keeps failing, you're not alone. See every Postman problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Postman errors
- Postman Could Not Get Response Error
- Postman Error: connect ECONNREFUSED
- Postman SSL Error: Self Signed Certificate
- Postman CORS Error in Web App
- Postman Collection Runner Limit: You've Exhausted All Available Runs
- Postman Collections Not Syncing
- Postman Lost My Collections
- Postman Slow and High Memory or CPU Usage