1. The Hidden Productivity Bottleneck in 2026
In the modern remote work era, tools like Notion and Figma have become the backbone of collaboration. However, for users in certain network environments, these tools often suffer from "micro-delays"—that annoying spinning wheel when opening a page or the "Syncing..." message that lingers too long in Figma. By 2026, as these applications become more complex with AI integrations and real-time multiplayer features, the network demands have only increased.
Using a standard VPN often doesn't solve the problem; in fact, it might worsen it by routing all your traffic (including local resources) through a single, congested tunnel. This is where Clash shines. By utilizing its advanced rule-based steering, you can ensure that only the necessary traffic goes through high-speed proxies while keeping everything else on a fast, direct path. This guide will walk you through the best practices to optimize your Clash workflow for maximum productivity.
2. Understanding Notion and Figma Traffic Shapes
To optimize them, we first need to know what we are dealing with. Both Notion and Figma are Electron-based or browser-based applications that rely heavily on WebSocket for real-time updates and CDN for asset delivery.
Notion's Footprint
Notion isn't just one domain. It uses notion.so for the main app, but loads scripts from www.notion.so, static assets from msgraph.com (for integrations), and various Amazon S3 buckets for user-uploaded images. If your proxy rules only cover notion.so, your images might still load slowly because they are being routed through a different, slower path.
Figma's Footprint
Figma is even more sensitive. It uses figma.com for the editor, but relies on static.figma.com for UI components and s3-alpha.figma.com for heavy design files. Furthermore, Figma uses multiple subdomains for its real-time collaboration engine. A laggy connection to the collaboration server means you'll see your teammates' cursors jumping around instead of moving smoothly.
3. Optimizing Clash Rules for Workflows
The secret to a smooth experience is Rule Granularity. Instead of using a generic "Global" mode, you should use "Rule" mode with specific domain-suffix matches. Here is a curated list of rules you should add to your Clash configuration (YAML) to ensure Notion and Figma always use your fastest nodes.
rules:
# Notion Specific Rules
- DOMAIN-SUFFIX,notion.so,PROD-WORK-GROUP
- DOMAIN-SUFFIX,notion.site,PROD-WORK-GROUP
- DOMAIN-SUFFIX,notion-static.com,PROD-WORK-GROUP
- DOMAIN-SUFFIX,notion.new,PROD-WORK-GROUP
# Figma Specific Rules
- DOMAIN-SUFFIX,figma.com,PROD-WORK-GROUP
- DOMAIN-SUFFIX,figmacdn.com,PROD-WORK-GROUP
# Supporting CDNs and Assets
- DOMAIN-SUFFIX,amazonaws.com,PROD-WORK-GROUP
- DOMAIN-KEYWORD,s3,PROD-WORK-GROUP
- DOMAIN-SUFFIX,cloudfront.net,PROD-WORK-GROUP
In the example above, replace PROD-WORK-GROUP with a policy group that contains your lowest-latency nodes (typically nodes in Hong Kong, Singapore, or Japan for Asian users, or local regional nodes for others). Using a url-test or fallback policy group is highly recommended here to automatically switch if a node goes down during a design session.
DOMAIN-SUFFIX,amazonaws.com. Since many apps use AWS, this might proxy more traffic than you intended. If you want to be more precise, use DOMAIN-KEYWORD,figma or specific S3 bucket URLs found in your Clash logs.
4. The Power of TUN Mode for Desktop Apps
Many users struggle because the Notion or Figma Desktop Apps sometimes ignore the system proxy settings. This is a common issue with Electron apps. While you can manually set proxies in some apps, the most robust solution in 2026 is TUN Mode.
TUN mode creates a virtual network interface at the OS level. Every single packet leaving your computer—whether from a browser, a terminal, or a standalone app like Figma—passes through Clash. This ensures 100% coverage without needing to configure individual applications.
How to Enable TUN Mode in Clash Verge Rev:
- Open Clash Verge Rev.
- Go to Settings -> Clash Core Service.
- Ensure you are using the Mihomo (formerly Clash Meta) core, as it has the best TUN support.
- Toggle TUN Mode to ON.
- (Windows Users) You may need to grant administrator privileges for the virtual network card to be created.
5. DNS: The Silent Killer of Speed
When you type figma.com, your computer first needs to find the IP address. If your DNS resolution is slow, it doesn't matter how fast your proxy is; the initial connection will feel sluggish. This is known as "DNS Lag."
In your Clash config, you should use the fake-ip stack for the best performance with TUN mode. This allows Clash to return a "fake" IP immediately while it resolves the real one in the background, significantly cutting down the time to start a connection.
dns:
enable: true
enhanced-mode: fake-ip
nameserver:
- 1.1.1.1
- 8.8.8.8
- https://dns.google/dns-query
fallback:
- https://1.1.1.1/dns-query
- tcp://8.8.8.8
6. Advanced Troubleshooting: Sync Issues
If you still encounter sync issues in Figma (e.g., "Disconnected" bar at the top), it is likely due to UDP traffic being blocked or MTU issues. Mihomo core handles UDP much better than the original Clash core. Ensure your proxy provider supports UDP relay, and set udp: true in your proxy configuration.
Another tip is to check the Connections tab in Clash. Filter by "figma" or "notion" and look for any red entries. A red entry means a connection was reset or timed out. If you see many connections going to DIRECT that should be proxied, your rules need adjusting.
7. Automating Your Workflow
Productivity isn't just about speed; it's about not having to think about your tools. By setting up Scripting or Sub-rules in Clash, you can create a "Work Mode" that activates automatically during business hours, prioritizing your work apps over entertainment traffic. This ensures that even if you have a background download running, your Figma canvas stays responsive.
In conclusion, optimizing Notion and Figma with Clash is a three-pillar process: Granular Rules, TUN Mode, and Optimized DNS. Once these are set, the "micro-delays" that plague modern web apps will vanish, allowing you to stay in the "flow state" longer.
"The best network setup is the one you forget exists. When Figma feels like a local app and Notion loads as fast as a text file, you've achieved peak Clash optimization."
Ready to transform your professional workflow? If you haven't yet, you can go to our download page to pick the right version for your system →
Ready to get started?
Download the latest Clash clients and apply these optimization rules to boost your Notion and Figma productivity today.