Batch image spoofer workflow for a client campaign
Organise original photos, choose image-spoofer settings, review a batch and hand approved variations to your posting team with a clear source record.
A useful batch starts with approved originals and ends with reviewed files assigned to a real job. Separate multiple versions of one image from processing a collection of different originals.
Decide what each batch means
Two requests can sound like “batch image spoofing” but need different workflows. One client may want five versions of a single approved photograph; another may want one prepared copy of each image in a shoot. Write down which job you are doing before you upload.
Media Variations supports one version or a supported batch of 5–50 versions from one original. Autospoof is intended for repeat work with saved originals. Check the current tool and plan limits rather than assuming that an output count is also an upload allowance.
| Request | Start with | Review decision |
|---|---|---|
| Five versions of one campaign image | One approved original in Media Variations | Which versions fit the planned posts? |
| Return to saved originals for another run | The current Autospoof workflow | Are these still the right source files? |
| A generated new pose from a photo | AI Retake | Does the generated subject and scene pass review? |
Keep source, client and destination together
Use a simple source identifier before processing. For example, campaign-a_hero-01 can remain the reference for all variations of that image. Keep the unedited file in a separate source folder and put downloads in a dated output folder.
Record who approved the source and what must stay visible. A product label, a logo near the edge or a required crop can change which settings are appropriate. This is a team handoff record, not a claim that Spoofzy automatically stores your campaign brief.
| Field | Example |
|---|---|
| Source | campaign-a_hero-01.jpg |
| Output | campaign-a_hero-01_v03.jpg |
| Settings | Record the chosen treatment and mirror choice |
| Review | Approved / reject / needs another version |
| Destination | Assigned account or post slot |
Approve one result before making more
Send the original as a Telegram file and try one result. Inspect the whole composition and the important details at full size. If it needs adjustment, change the available settings and review again before choosing the larger batch.
Use the same acceptance criteria for every output: readable text, correct subject, suitable framing and a file the posting team can open. A successful download means the file arrived; it is not the same as creative approval.
Source: Image spoofer quality checklist
Download, review and assign the usable versions
Save the finished files using the available individual or ZIP download controls. Preserve their link to the original when you rename them. Do not overwrite the source with the first output you download.
For a practical five-version job, mark each result approved or rejected, then assign approved files to the actual post plan. Pair them with relevant copy and context. Preparing variations does not automatically publish anything or guarantee a platform outcome.
Make the next operator's job easier
Leave the source identifier, selected settings and review notes together. Linked teammates use their own Telegram accounts under the owner's plan, and supported settings are account-specific. Do not assume a teammate inherited the settings you used.
For browser work, open Spoofzy Cloud and follow the current workspace controls. For repeated work from saved media, review Autospoof's current access and limits. Keep the workflow description specific to the interface your team uses.
Source: Share Spoofzy with your team
A batch your team can actually use.
Start with approved originals and finish with reviewed versions that have a clear destination.
Explore batch image variations