How to Use Figma AI Image Selection on Windows in 2026?

Figma’s November 6, 2026 release notes list the AI image selection update as available only in the macOS desktop app (Figma release notes). So if you’re using Figma in a Windows browser or desktop workflow, don’t treat a missing entry as proof that your file is broken: the documented platform boundary is the first thing to check. A remote Mac is a possible way to test the macOS workflow, not a guarantee that the feature will appear or work for your account.

Who should read this: Windows-based graphic and UI designers who want to isolate or remove an object from an image in Figma.
Freelancers without a Mac can use the validation steps to assess a remote workflow before putting a client file through it.
Creative leads deciding whether to arrange temporary macOS access can use the same checks as an acceptance test.

Last updated November 7, 2026. Platform information checked against Figma’s release notes and desktop app download page. Those pages can change; recheck them before committing a production task.

Start by separating the platform limit from a product fault

The current release note identifies the AI image selection update as macOS desktop app-only. It does not establish that the same entry is available in a Windows browser, or that a remote Mac will expose it for every account. That distinction matters: troubleshooting a Windows browser for an entry that is not documented for that workflow can waste time without resolving the actual constraint.

Can you use Figma AI image selection on Windows?
Not directly in the Windows workflow covered by the current platform note. If you need this particular entry, test it in the macOS desktop app. Keep using your current Windows workflow for ordinary design work unless the macOS-only function is necessary for the task.

Where should you look for the feature in the web version?
Don’t assume there is a web menu to find. The release note names the macOS desktop app, not the browser, as the platform for this update. First distinguish whether the file is open in Figma Design in a browser or in the macOS desktop app; then check the official desktop app guide and the download page for the current app information.

A platform limitation is not the only possible explanation for a missing control. The file may be open in the wrong product or environment, the user may not have permission to edit, or the feature’s availability may not match what you expected. Figma’s file and folder permissions guide explains how access settings affect work with shared files. It does not prove that a particular account has the AI feature, so treat account eligibility as something to confirm rather than assume.

Check the macOS desktop route before changing your workflow

If the feature is important enough to justify a platform test, begin with official information rather than installing software or moving a client file based on a guess. The Figma desktop app download page provides the current download route, while the desktop app guide describes the desktop app. Recheck both when you begin: a release note describes a feature update, while app and product pages may change independently.

Does a remote Mac run Figma AI image selection?
It may let you test Figma in a macOS desktop environment, but that does not confirm that the feature will appear in your session. The release note confirms the platform boundary; it does not certify a remote Mac, a specific account, a particular file, or the availability of the control in every session. Check the live entry before assigning real work.

That caveat applies equally to the phrase “Figma Design macOS desktop app.” It identifies the environment to investigate, not a guarantee that a feature is enabled for a given user. If the entry remains absent after opening the correct app, check whether you can edit the file, review the official feature guidance, and note the app and account context. Avoid inferring an unpublished eligibility rule from a missing control.

Before testing, make a copy of a non-sensitive file or use a disposable test file. Figma’s file and folder permissions documentation helps you distinguish view access from the permissions needed to make changes. If the file owner has also restricted copying or sharing, review the official restrictions guide before assuming that a copy or export should be available.

Use this decision branch:

• If the macOS desktop app shows the entry in a file you can edit, test it on a reversible image and continue only if the result meets the task.
• If the entry is absent, check the current official release and app information, verify file access, and record what you see. Don’t treat remote access itself as proof of eligibility.
• If you only need a one-off visual change, compare the time and quality of your existing editing method before setting up another environment.
• If the task depends on the specific Figma AI control, pause delivery assumptions until the entry, edit, and export have all passed a real test.

The choice is not simply “Windows or Mac.” A browser-based workflow may be adequate for the rest of the design file, while the image operation may need separate verification. A remote Mac introduces its own dependencies: network stability, access to the right file, and a reliable handoff of the exported asset. Those are reasons to test the entire path, not just the first screen.

Diagnose a missing entry without guessing

Once you are in the macOS desktop app, check the problem in a fixed order. Start with the product and app environment, then permissions, then the current feature information. This avoids mixing a platform question with a file-access problem.

Step 1: Confirm the environment. Check that you are in the macOS desktop app rather than a Windows browser or Windows desktop app. Use Figma’s desktop app guide if you need to confirm which app you opened.

Step 2: Confirm that the file is editable. A control that changes an image is not useful if you only have viewing access. Ask the file owner to check the file’s permissions, or compare your access with the official permissions guidance.

Step 3: Check current feature instructions. Figma’s AI image editing guide is the appropriate place to verify the current documented workflow. Don’t substitute a menu path remembered from another feature or an older interface.

Step 4: Record what is actually visible. Note the app environment, the account context you can verify, the file’s edit access, and whether the entry appears. This is more useful than reporting only “AI is missing,” especially when asking an administrator or file owner for help.

Step 5: Stop if the official information does not resolve it. If the feature page and release note do not clarify your situation, wait for confirmation or test later. Do not convert an unverified assumption about account eligibility into a production plan.

A small record can keep the test factual. The block below is a blank reporting format, not a command to run and not a claim that ViewMini has tested a particular environment:

Environment: [Windows browser / Windows desktop / macOS desktop / remote Mac]
Figma app or browser details: [record what is shown]
File access: [view / edit / not confirmed]
AI image selection entry: [visible / absent / not checked]
Test image: [reversible copy / original]
Selection checked: [yes / no]
Export opened and reviewed: [yes / no]
Result: [pass / fail / needs confirmation]

For example, a useful result might read: Environment: remote Mac; entry: absent; file access: edit; result: needs confirmation. That wording records an observation without claiming that remote Macs are unsupported or that the account is ineligible. If the entry is visible, record that too, but do not generalize one successful session into a universal availability promise.

Test the selection and preserve the original

Finding a control is only the start. The design task is to isolate or edit the intended object, and the output must still work in the design file and in the handoff. Figma’s AI image editing guide should be used to confirm the documented operation. Avoid assuming that “select,” “isolate,” and “erase the background” describe the same result.

Pick a representative image that resembles the real work: similar subject, overlapping elements, and edge complexity. Use a duplicate or another reversible copy, and keep the original untouched. Inspect the boundary around the target at a size where small edge errors are visible. Check whether unwanted parts remain, whether intended parts disappear, and whether the result is suitable for the specific layout. A result that looks acceptable as a thumbnail may still fail when placed against a contrasting background or scaled for delivery.

How should you check an AI-selected image object before exporting?
Compare the edited result with the original and check the edges, overlaps, and any small details the design depends on. Then save the result in the file and export a copy for inspection. Figma’s static design export guide explains the official export workflow; it does not guarantee that a particular selection will meet a client’s quality requirements.

Keep the scope narrow. This is an image-editing aid, not a basis for promising complete retouching, professional-grade masking, or lossless delivery. Complex edges and layered imagery deserve human review. If the target is for client delivery, compare the exported file against the original and the brief before replacing any existing asset.

Run one acceptance test before choosing a remote workflow

A remote Mac can be worth evaluating when a project genuinely needs a macOS-only entry, but only an actual session can answer whether the route works for the intended file and account. The acceptance test should cover the whole path, not just whether a desktop appears.

1. Choose one representative, reversible image. Avoid beginning with a deadline-critical or confidential source file. Use a copy you can discard.
2. Open the macOS desktop app and confirm the entry. If it is not present, record the environment and stop treating the feature as available.
3. Check the file’s edit access. Resolve permission questions with the file owner before interpreting a failed edit as a software issue.
4. Select or edit the intended object. Compare the result with the original, including edges and overlaps that matter to the design.
5. Save and export a copy. Follow Figma’s static export guidance, then open the exported file and inspect it outside the editing canvas.
6. Check the handoff. Confirm the recipient can access the file and that the exported asset is the version expected. If copying or sharing restrictions apply, check Figma’s file restrictions documentation.
7. Choose a workflow from the evidence. Keep using Windows if the feature is unnecessary; use a verified macOS route only if the entry, edit, and export all pass; otherwise use another editing method or wait for clearer feature information.

This is also the point to consider whether the image is actually the bottleneck. If the task is a simple, occasional cutout, the time spent arranging another environment and transferring files may outweigh the benefit. If the task repeatedly depends on the specific Figma AI image selection control, a short remote Mac test may be more practical than buying hardware before you know the workflow is viable.

Choose between Windows, a remote Mac, and another method

There is no universal winner. Choose the current Windows route if it meets the brief. Choose a remote Mac test only when the macOS desktop app is necessary and you can verify the feature and the handoff. Consider local hardware when macOS work is a sustained part of the business rather than an uncertain, occasional need.

For a short evaluation, ViewMini’s Mac options can be compared with the cost and effort of using existing equipment. If a project needs a particular environment, confirm the available option and access details before scheduling work; the product page is not evidence that Figma’s feature will appear in a specific session. A Mac mini option in Hong Kong is one page to review when comparing locations, not a recommendation that a particular location will provide a better image-editing result.

For a team, the main hidden costs are not just hardware. A remote workflow can add file-transfer steps, network-dependent interaction, permission checks, and a second review of the exported asset. These costs are manageable for a short, verified task, but they weaken the case if every image needs repeated changes or the network makes precise inspection uncomfortable. If access or delivery requirements remain unclear, resolve them before committing a client deadline; a direct inquiry to ViewMini can clarify service questions, but cannot confirm Figma feature eligibility.

If Windows is currently workable, replacing it just to chase an unverified entry is premature. If you need the macOS desktop workflow only for a defined project, buying a Mac may leave you with hardware to maintain after the need ends. A ViewMini rental is worth considering for a temporary test when you want to avoid that purchase, but it still has real trade-offs: remote interaction depends on your connection, files need a deliberate handoff, and the feature must be verified in the actual session. Start with one reversible image, confirm the entry and export, and only then decide whether a short-term Mac workflow is better than staying on Windows or using another editing method.