Builder review7 min readUpdated June 5, 2026

Carry over original buttons and images

Decide when to include InfoPath buttons, picture buttons, logos, and large images in the generated app.

Quick answer

In short

Buttons and images can be carried over automatically, but they should be optional because some forms use large decorative assets that make the generated canvas harder to use.

Most likely cause

Content can be pushed off screen when too many imported visual assets are placed above the generated form area.

What to do next

Use Required Settings to choose whether to add original buttons and images. Disable images for clean data-entry forms; keep buttons when their navigation rules are useful.

When to keep buttons

  • The button switches views or virtual screens.
  • The button triggers a simple save/submit action.
  • The original form used labeled workflow buttons users will recognize.

When to skip buttons

  • The button opened a legacy URL or script path no longer available.
  • The button duplicated a standard save action you will rebuild differently.
  • The generated app should use a new navigation model rather than the InfoPath layout.

When to keep images

  • The image is a logo or user-recognizable header.
  • The image is a confirmation or instruction graphic that carries meaning.
  • The media asset helps makers rebuild the screen accurately.

When to skip images

  • Large decorative images push data-entry content below the canvas.
  • The organization wants a new app-style interface rather than a pixel copy.
  • The image is missing from the package or low quality.

Keep reading the next most relevant guides for this form pattern.