What a shared template form is
Instead of exporting a design file and hoping someone edits it correctly, you publish a template as a form. The person on the other end sees a simple page - swap a headline, drop in a photo, pick from an approved color set - and downloads a finished image. Picnie generates the form directly from a template you build once.
Who this is actually for
- Franchise or multi-location brands that need every store making the same flyer with local details.
- Agencies handing a self-serve social template to a client instead of a new request each week.
- Sales and recruiting teams building personalized outreach graphics without opening a design tool.
- Event or real estate teams where dozens of listings need the same layout with different photos.
Decide what stays locked and what opens up
The value of a shared form is control, not freedom. Before publishing, decide exactly which layers are editable - usually a name, a headline, a photo, maybe a date - and lock everything else: logo position, fonts, brand colors, layout spacing. Anyone filling the form can only change what you allow, so the output always looks on-brand even if the person filling it in has no design sense.
Publishing the form
- Finish the template design and mark which fields are user-editable.
- Generate the shareable link from the template settings.
- Send that link to the client, franchisee, or team member - no Picnie account required on their side.
- They fill the open fields and export the finished image directly.
What it looks like on the client's side
The person opening the link sees only a clean fill-in form: labeled fields, a live preview of the template updating as they type, and a download button. There is no layer panel, no undo history to worry about, and nothing to accidentally break. That simplicity is exactly what makes non-designers comfortable using it.
Collecting what comes back
Every export can be tracked back to the template it came from, which matters once ten locations or twenty sales reps are all using the same link. Rather than chasing files over email, you know the source template and can spot-check outputs for consistency, or pull them into a shared folder for a specific campaign.
Keeping control without reviewing every file
Because the risky parts of the design - brand colors, logo, layout - are locked at the template level, you do not need to manually approve every single export. Update the master template once and every future link inherits the change; past exports simply stay as they were generated.
Versioning without a formal version history
Shared forms do not usually need a full version history to stay manageable. A simpler habit works almost as well: keep a dated note of when the underlying template last changed, so if a client asks why last month's export looks slightly different from this month's, you have an answer without digging through file history. Because past exports are static images, nothing about them changes retroactively - only the form going forward reflects the update.
A quick example worth adapting
A regional retail brand with forty locations can hand each store manager one link tied to a "this week's promotion" template. Store managers fill in a local start date and swap the featured product photo; everything else - the brand colors, the logo, the legal disclaimer line - stays exactly as corporate approved it. No file gets emailed back and forth, and no manager needs to know anything about design software to produce something that looks correct in a shared folder review.
What a shared form is not a replacement for
A shared form works because the range of allowed changes is narrow. It is a poor fit for genuinely custom design requests - a one-off event graphic with an unusual layout, or a client asking for something the template was never built to support. Keep a normal design request path open for those cases rather than trying to stretch one flexible template into covering every possible ask; the value of the form comes specifically from how constrained it is.
Start sharing on Picnie
Build the base design in Create Images Online, lock the brand elements, and share the form link with anyone who needs to generate their own version. For teams generating from a spreadsheet instead of a form, the same template works with Picnie integrations or the API.
Picnie at Picnie. Writes about image automation, developer experience, and shipping product faster.