Foto Master

How to Use the QR Code Workflow Step in FMX for Windows

Updated Today · 4 min read

The QR Code workflow step gives guests a scannable link during the FMX experience. It can open a Foto Master Cloud gallery or media page, or send the guest to a Custom URL operated by you or your client.

Custom destinations can optionally include the filename of media produced in the current session. This is useful when a website, ordering system, or custom app needs to know which photo or video belongs to the guest.

This is a sharing QR step, not a payment QR. Stripe and Shopify checkout QR codes are configured through Payment triggers and Payment Selection Screens.

1. Add the QR Code Step

  1. Open the workflow in Foto Master Cloud.
  2. Add QR Code from the Cloud steps.
  3. Place it after the media that the QR should reference.
  4. Connect it to the next step in the guest flow.
  5. Select the node to configure its triggers, destination, and colors.

2. Choose How the QR Screen Continues

  • Touch trigger: The guest taps to continue after scanning.
  • Time trigger: FMX continues automatically after Timeout (sec).
  • Touch and Time: The guest can continue early, or FMX continues when the timeout expires.

When Time is disabled, Touch remains available so the guest cannot become trapped on the QR screen. Enabling Time turns Touch on by default; you can keep both or use the timed behavior provided by the Builder.

3. Choose a Destination

Cloud destination

Choose Cloud when the QR should open a Foto Master-hosted destination.

Under Link to, choose:

  • Media Landing Page: A page for a selected session media type.
  • Gallery: The event gallery.

For Media Landing Page, select Final Photo, Final Video, Final GIF, Raw Photo, or Raw Video.

Cloud QR media creates a Cloud Sync requirement. When the event starts, FMX checks the matching media toggle under Global Settings > Cloud and can offer to enable it for the current start attempt.

Custom destination

Choose Custom and enter the full Custom URL when the QR should open your own website or app.

If the scheme is omitted, FMX normalizes the address to HTTPS. Use a complete HTTPS URL and scan it with the actual guest phones before the event.

A Custom destination does not require FMX Cloud media upload unless another workflow step requires it.

4. Add a Dynamic Filename to a Custom URL

Enable Add file name after the URL, then configure:

Media

  • Final Photo
  • Raw Photo
  • AI Photo
  • Raw Video
  • Final Video
  • Final GIF

For Raw Photo, AI Photo, and Raw Video, FMX uses the most recently produced matching item in the current session.

File name format

FormatExample
?q={filename}https://your.site/page?q=final_photo_001.jpg
/{filename}https://your.site/page/final_photo_001.jpg

If the base URL already contains a query string, FMX adds the filename with an ampersand instead of creating a second question mark.

Include file extension

  • Enabled: final_photo_001.jpg
  • Disabled: final_photo_001

The filename is safely encoded before it becomes part of the URL.

Node Ordering Matters

FMX can append a filename only after the selected media exists.

Examples:

  • Place a Final Photo filename QR after the Final Photo has been rendered or saved.
  • Place an AI Photo filename QR after the AI service and its AI Processed wait.
  • Place a Final Video filename QR after video processing completes.

If the selected media does not exist when the QR is built, FMX uses the base Custom URL without a filename rather than showing a broken QR.

5. Configure Scan-Safe Colors

Set:

  • QR color: The dark code modules.
  • Background color: The light solid background and quiet zone.

The Builder displays Scan Reliability as Excellent, Good, or Risky. Saving is blocked when the colors are too risky to scan.

For reliable results:

  • Keep the QR darker than the background.
  • Prefer black or a dark brand color on white or a very light background.
  • Do not use transparent, patterned, or moving media directly behind the code.
  • Use Auto Fix: Swap colors when the foreground and background are reversed.
  • Scan-test the design on several iPhone and Android devices.

6. Save, Sync, and Test

  1. Save the workflow.
  2. Sync the event to FMX for Windows.
  3. Produce the selected media through the real workflow.
  4. Scan the QR from the booth display.
  5. Confirm the destination opens on a phone using cellular data as well as event Wi-Fi.
  6. For a Custom URL, inspect the resulting address and filename.
  7. Test Touch, Time, and timeout behavior.
  8. Start a second session and confirm its QR does not reuse the first guest’s filename.

Troubleshooting

The QR opens the base URL without a filename

  • Move the QR step after the selected media is produced.
  • Confirm Add file name after the URL is enabled.
  • Confirm the session contains the selected media type.
  • For AI Photo, wait for AI processing before showing the QR.

The QR is difficult to scan

  • Increase foreground/background contrast.
  • Keep a solid light background around the code.
  • Increase the displayed QR area.
  • Avoid glare and excessive display brightness.

Cloud QR shows the wrong media

Confirm Link to > Media Landing Page and the selected Media type, then confirm the matching Cloud Sync toggle is enabled.

A phone cannot open the Custom URL

Test the URL outside FMX, confirm HTTPS and DNS are valid, and make sure the destination is publicly accessible rather than available only on the booth computer’s local network.

The timeout never continues

Enable Time trigger, enter a positive timeout, save the workflow, and sync the updated event.

Was this helpful?

Related articles