CartVisualCreate account

Does a Photoroom Web App export default belong to one Space, the user, or the team?

The Photoroom Web App export default is personal and spans all Spaces accessible to that user. Choosing it while viewing one Space does not make it a setting for only that Space, and colleagues in the same Space may have different defaults. Configure it for a repeated personal download pattern; preserve each destination’s delivery-format requirement separately.

Published · By CartVisual editorial team

Draw the scope correctly: one user, many Spaces

In Photoroom Web App, open Preferences, choose Settings for any Space, select the default file format, and exit with X. The key scope rule is easy to misread: the choice becomes your default across all your Spaces, while other people can select a different format even in the same Space.

Therefore the Space used to reach Settings is not a separate format policy boundary. A shared Space cannot serve as evidence that an exporter has the team’s approved format selected. Likewise, moving from a merchandising Space to a designer-handoff Space does not by itself change your own default. Think of the setting as a convenience for the person downloading, not metadata attached to the Space or the design.

For a team, record the delivery contract in the handoff: destination, accepted format, transparency requirement, final filename, and person approving the received file. This is deliberately separate from the question of whether JPEG, PNG, or WebP suits the destination, which the existing format-delivery guide already answers.

Set a personal default only when exceptions stay visible

A repeated, predominantly opaque-photo workflow may justify a JPEG default; frequent transparent cutout handoffs may lead to a different personal preference. These are illustrative workflow choices, not a claim that Photoroom automatically detects asset types or changes formats for exceptions. The cited article establishes the default setting, but does not specify per-download override mechanics.

Before each handoff, compare the needed format with the format actually offered and downloaded. If they differ, resolve the export-format selection through a supported route before sending the file. Do not rename an extension, assume a teammate inherited your choice, or claim that changing a preference alters files already downloaded.

If a seller alternates continuously among incompatible delivery contracts, the safer operational rule is to explicitly verify each output rather than using any one saved preference as approval. The presence of a default reduces a recurring menu decision; it cannot enforce marketplace requirements or describe how a remote platform will render the upload.

Illustrative example: one editor, two Spaces, two recipients

An editor usually exports opaque catalog photographs for Space A and chooses JPEG as their personal default there. Later they move to Space B, where a designer needs a transparent cutout. Because the default follows the editor across Spaces, Space B is not a reason to assume that PNG will be selected. The editor checks the actual export format and withholds the handoff until an appropriate file has been produced.

A colleague opening Space A does not inherit the editor’s JPEG choice as a team rule. The colleague verifies their own selection against the catalog brief. The two required actions are independent: the first person checks a cross-Space exception; the second checks a different user’s preference.

Where CartVisual fits

The browser-local manual checklist is relevant for inspecting downloaded product-image evidence before delivery, not for configuring personal export preferences.

See the current CartVisual workflow and its limitations

Source and evidence scope

Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.

Photoroom: Set the default file format for exports (Web App)

Official source snapshot checked .

The official Web App instructions establish how to choose a default export format and specify its personal, cross-Space scope. They do not document team-wide enforcement, per-download override controls, mobile preference synchronization, previously downloaded file changes, or destination-specific acceptance and rendering.

Related decisions

Browse ecommerce creative workflows