Update a Figma Design Preview Without Sending Your Client a New Link

A stable client preview link makes it easier to return to a design after revisions. In Swelik, you can import a newer Figma frame into an existing project from its private management page. The public project URL stays the same while the selected design is replaced.

The update is manual. Editing the Figma file alone does not change the Swelik preview. That separation lets you decide when a revision is ready for the client, but it also means the review message should identify what was imported and when.

Start from the existing management link

Open the private management URL saved when the preview was created. Do not create a new project from the homepage if your goal is to update the existing client destination. A new project is a different preview with its own link.

Confirm the project name and open its current public preview before making a change. This is a useful check when several client projects have similar names. Keep the management URL out of any message intended only for reviewers.

If you no longer have the management link, do not expect the public URL to reveal owner controls. The public preview is designed for viewing. Follow the available owner-support process rather than attempting to modify a project through a client link.

Prepare the revision in Figma

Identify the frame that represents the next review version. Check that the requested changes are present and that unrelated experimental work is not part of the export. Use a clear frame name so it is recognizable in the import list.

If you maintain separate desktop and mobile designs, confirm which one changed. A desktop revision may not imply that the mobile layout has been updated. Keep a simple list of the layouts included in the current review round.

For significant changes, retain an appropriate record of the previously reviewed artifact and decision. A stable URL points to the current design; it should not be treated as proof that the content behind it has never changed.

Import into the correct device target

In management, use Update from Figma. Enter the design link and the required access token, load the frames and select the intended frame. Then choose the device target before confirming the update.

The target matters. Importing a narrow mobile frame into the desktop slot does not create a mobile tab. It replaces the desktop design with the selected export. Check the device selection deliberately, especially when using similarly named frames.

Swelik prepares the new design before activating the replacement. A failed import should leave the earlier active design available. If the operation reports a processing issue, inspect the management status and follow the recovery guidance rather than assuming the update succeeded.

Verify the public result

Open the same public URL after the update and select the relevant device tab. Check a visible change that distinguishes the new revision from the old one. Review the beginning and end of a tall design so a partial or incorrect export does not reach the client unnoticed.

Confirm that the other device layouts still represent the intended state. A mobile update should not be described as a complete website revision if the tablet and desktop designs remain unchanged. Make that scope explicit in the review message.

If the old design still appears, refresh and verify that you updated the correct project and device. Do not immediately create a second project as a workaround; first establish which artifact the current public page is displaying.

Send a revision note, even though the URL is unchanged

Tell the client that a new revision is ready and summarize the relevant changes. Ask them to check the issues addressed in this round. A message that only repeats the same URL does not explain what requires attention.

For example: “Homepage mobile revision 3 is ready at the same preview link. We clarified the service area and moved the enquiry action above the FAQ. Please confirm those two points. The desktop layout is unchanged in this round.”

Keep the scope of any approval clear. The project review status and the designs included in the request need to be understood together. Do not interpret a response to one device as approval of layouts the client has not reviewed.

Keep a useful revision record

Record the revision label, device, import date, significant changes and the review outcome. A short record is usually enough to help the next person understand the sequence. Use the revision log template if your current notes are scattered across messages.

Version history can help an owner inspect earlier artifacts, but it is still important to understand the controls before restoring anything. In the current workflow, device updates use their device target; the existing restore action restores the desktop design. Do not use a desktop restore as a substitute for selecting the correct device update.

When discussing an older comment, refer to the revision it concerned. A section may have moved or disappeared. Preserve the underlying concern rather than assuming that an old location still identifies the same element.

Use a PDF replacement when the API is unavailable

If Figma export cannot complete, export the frame manually and upload the resulting PDF to the appropriate device through management. The goal is to update the existing project, not to require a particular import method at every revision.

Check the manual export using the same visual review steps. Keep the original file and note the revision so the client can still understand the update. See Figma import troubleshooting for the relevant failure stages.

Frequently asked questions

Does Swelik watch my Figma file for changes?

No. You initiate each import. The public preview changes after a successful update, not every time you edit a layer in Figma.

Can I update only mobile?

Yes. Select the mobile target in the management workflow and import the appropriate frame. Verify the mobile tab afterward and state the limited revision scope in the client message.

Should I send the management link with the update?

No. Send the existing public preview link. Keep the management URL private because it provides owner actions.