A Windows Figma workflow is ready, but Select area is missing from the image-editing options.
Fast answer: As of November 10, 2026, Figma says Select area is available only in its macOS desktop app, so Windows users cannot invoke it directly. If you repeatedly need its image isolation or erasing work for delivery, compare a Mac you own, a remote Mac you have verified, and your existing tools. If you only need it occasionally—or only need ordinary Figma browser collaboration—don’t rent a Mac just for this feature.
This guide is for UI designers who want to know whether the restriction changes their Windows workflow; visual designers who often clean up image details; and freelancers or team leads deciding whether a Mac step belongs in project delivery.
Last updated November 10, 2026. The platform boundary and feature description were checked against Figma’s Select objects announcement, its image editing guidance, and its desktop app guide.
01 What the Windows limitation means for your Figma workflow
Figma’s November 6, 2026 announcement describes Select area as a way to select objects in an image for isolation or erasing, and says the feature is available only in the macOS desktop app. That establishes the platform limit for this feature. It does not mean that all Figma work requires a Mac, or that every Figma AI image-editing feature has the same restriction. Check the current Figma AI image editing documentation for the particular tool you plan to use.
Can you use Figma Select area on Windows? Not directly, according to Figma’s announcement. You can keep using your existing Windows workflow for Figma tasks that work in your browser, but you should not plan a Select area step there unless Figma updates its platform support. Figma’s desktop app guide is the official place to check desktop app information.
Keep these activities separate when estimating the impact:
- Browser-based collaboration: Reviewing or editing shared Figma files is a different task from invoking Select area. Figma’s file and prototype sharing guide explains how shared files and prototypes are handled.
- Image-local editing: Select area is the specific image-selection and isolation-or-erasing capability identified in the announcement.
- Design-file delivery: A Figma file may still be editable and shareable without this particular image operation. Your delivery responsibility determines whether a separate image-editing step is necessary.
- Mac access: Having access to macOS does not itself confirm that your account, app version, project permissions, or remote setup is eligible. Verify those conditions before promising the feature to a client.
Figma’s AI FAQ is also relevant when you need to confirm availability or account conditions. Do not treat a feature announcement as a guarantee that every account or project can use the feature.
02 For Windows-first UI designers, keep the Mac decision narrow
If your daily work is interface layout, component editing, prototyping, and browser-based review, the platform restriction may have little effect on your main workflow. The decision is whether Select area solves a recurring image task that your current process handles poorly—not whether Figma as a whole requires macOS.
Why does Select area require the macOS desktop app? Figma’s announcement states the supported platform, but that statement alone does not explain the technical reason. Don’t infer that Windows browsers are generally unsuitable for Figma AI, or that other image tools share the same restriction. Check the official feature and desktop-app pages for updates before changing your process.
For a UI project, identify the exact point where the feature would be used. Is it a one-off cleanup of a photo in a hero section? A repeated operation on product imagery? A client requirement to deliver a particular edited asset? If the task is occasional and the existing result is acceptable, the platform limit may be an inconvenience rather than a reason to arrange Mac access.
A practical boundary is to keep interface design and shared-file review in your current setup unless the image-editing task itself requires Select area. This avoids making every collaborator’s workflow depend on a Mac for a feature only one person may need.
03 For visual designers, test the image before changing tools
Select area is intended to help isolate or erase objects within images. That describes its purpose; it does not guarantee a clean result on every source image. Busy backgrounds, overlapping objects, fine edges, and low-quality source material can all make an edit harder to accept. Judge the result against your actual asset and delivery standard, not a feature description alone.
Before arranging a Mac workflow, choose a representative image from a real project. Preserve the original. Then record what “good enough” means for that asset: clean edges at the intended display size, no visible remnants, acceptable texture around the edited area, and a file that can still be handed off as required. Compare the result with your current image editor or manual retouching process.
Is Figma AI image editing the same thing as Select area? No. The announcement identifies Select area as a particular way to select image objects for isolation or erasing. Figma’s broader AI image editing help covers related image-editing capabilities. Check the requirements for the exact operation you need; do not assume one feature’s platform limit applies to all of them.
If the selected area needs further refinement outside Figma, include that work in your comparison. An edit that looks acceptable on the canvas may not meet the client’s needs when exported, resized, or placed over a different background. The relevant question is whether the full result passes review, not whether the first selection appears convenient.
04 For product designers, separate image edits from design-file delivery
A product designer may own the Figma file, coordinate review, and deliver an editable design system. Those responsibilities do not automatically make Select area a required step. Keep the image edit, the design-file changes, and the final handoff as separate acceptance items.
Use the existing Windows workflow when the requested deliverable is a Figma file and the image can be supplied or edited through an already-approved process. Add a Mac step only when the project specifically requires Select area, the result needs approval, and no acceptable alternative fits the deadline or quality bar.
For handoff, confirm who owns the original image, who approves the edited version, and where the approved asset belongs in the design file. Figma’s file and folder permissions documentation can help you check whether the people assigned to edit or review have the access they need. A Mac environment does not fix missing file permissions or unclear ownership.
A clean handoff should make the asset’s status clear. Keep the source available, label the approved output, and identify whether the next person is expected to edit the image or only use it in the layout. This prevents a platform workaround from becoming an undocumented production dependency.
05 For freelancers, let project frequency and revision risk decide
A freelancer’s decision is often project-specific. One client may never request local image edits; another may expect repeated object isolation and close review. Look at actual briefs, revision history, asset volume, and delivery requirements before treating Select area as a regular operating cost.
Is it worth renting a Mac for occasional Select area work? Usually not if the job is rare, your current process meets the brief, and the client does not require this specific feature. Consider a Mac option only when the task recurs, the feature materially improves an accepted deliverable, and you can verify that the required app and account conditions work before relying on it.
When estimating a project, include the time needed to prepare the file, access the app, test the edit, save the result, and return it to the client’s workflow. Also consider the cost of a failed test or a late revision. Do not assume a short task means a short rental period or a predictable total cost; check actual service terms and project timing.
If the client requires a specific process, confirm that requirement before you quote. If the client only needs a clean image and an editable Figma file, compare the output standard rather than selling a particular tool workflow.
06 For small teams, assign the Mac step only to the right role
A mixed-device team does not need to move every designer onto macOS just because Select area is limited to the Mac desktop app. Decide who will make the image edit, who will inspect it, and who will update the shared design file. Then verify that the handoff between those roles is workable.
Use this team check before adding a Mac step:
- Name the person responsible for the source image and its approved edit.
- Confirm which account and project permissions that person needs.
- Agree how the edited asset returns to the shared file and who checks it.
- Test a representative project before promising that a remote environment will work for production.
- Keep a fallback image workflow available if access, eligibility, or the result fails review.
Figma’s file and folder permissions guide is useful for checking collaboration access. But access to a file is not proof that Select area will be available in a particular account or remote setup. Verify the feature itself with the intended account before assigning a deadline or making it a team dependency.
07 Use this decision branch before arranging Mac access
Choose the route that matches the task you actually need to deliver:
- If Select area is occasional and your current image process passes review, keep the Windows workflow. Do not add a Mac step just to access a feature you rarely need.
- If Select area recurs and the current output fails the brief, test a representative image in an eligible macOS desktop-app setup before committing to a production workflow.
- If the project depends on remote Mac access, verify app availability, account eligibility, file permissions, access method, saving, and return of the edited asset. Treat each as a separate check.
- If you need the feature continuously for long-running work, compare a Mac you own with a verified remote option and your existing alternatives. Include access continuity, revision handling, and the ability to complete the whole delivery loop.
- If the work is ordinary Figma browser collaboration, keep using the browser workflow unless another requirement—not Select area—calls for a Mac.
A remote session is not a compatibility guarantee. Before paying for any service, check its current access methods and conditions against your app, account, project files, and delivery needs. CALMVPS’s current service and plan information should be checked directly; do not assume a Mac rental includes a Figma license or that a particular account can use every feature.
08 Compare the workflows against the job, not the device
The main alternatives differ in what they require from you. A Windows workflow minimizes setup when the current tool already meets the quality bar. A Mac workflow may be worth testing when Select area is a repeated, required part of the edit. A remote Mac can avoid buying hardware for a limited need, but only after you confirm the application, account, file access, and delivery process.
| Workflow | Best fit | Check before committing | Main risk |
|---|---|---|---|
| Keep the Windows workflow | Occasional edits or browser-based Figma work | Whether the current edit meets the client’s quality and format requirements | Manual work or a substitute may not match the requested result |
| Use a Mac you own | Recurring work where local access and continuity matter | macOS desktop app, account eligibility, project permissions, and file handoff | Hardware cost and maintaining a separate device |
| Test a remote Mac option | A recurring but limited need when you do not own a Mac | Current service conditions, app access, account eligibility, saving, and return of files | Remote access does not prove feature or workflow compatibility |
CALMVPS’s order information is a place to check current service options, but confirm the relevant terms before you plan a client project around them. Compare the total workflow rather than assuming remote access will be faster, cheaper, or compatible for your specific files.
| Project condition | Recommended decision | Before delivery |
|---|---|---|
| Select area is not required and current image editing passes review | Stay with the existing Windows process | Confirm the exported asset and Figma file meet the brief |
| Select area is requested once, with an acceptable fallback | Use the fallback unless the client explicitly requires this feature | Agree on the output standard and retain the source |
| Select area is requested repeatedly and alternatives fail review | Validate a Mac workflow on a representative file | Check account, app, permissions, save, export, and handoff |
| A team shares the work across Windows and Mac users | Assign one owner for the edit and one reviewer | Document where the approved asset lives and who can access it |
If you only need standard Figma collaboration, a Mac adds an unnecessary dependency. If Select area repeatedly appears in accepted deliverables, first verify the complete edit-and-handoff loop; then compare a Mac you own with a remote option and the cost of continuing your current process. Renting through CALMVPS may suit a temporary, verified need better than buying hardware, but only if the app, account, project permissions, and service conditions match your job. Check the CALMVPS plan details before you commit.