Portfolio dataset note
What one recent 3200KStudio intake shows about planning still photography, finished product video, vertical social edits, reusable B-roll, 3D animation, and web-delivery files as one coordinated asset system.
Scope: 79 source assets from one recent portfolio intake: 46 photographs and 33 videos. This is a descriptive studio sample, not an industry benchmark, buyer-behavior study, or claim about sales performance.
The format split
| Video role | Count | Planning implication |
|---|---|---|
| Finished horizontal product or lifestyle video | 20 | Primary edits were usually planned for product pages, websites, Amazon, presentations, or landscape viewing. |
| B-roll clips | 6 | Reusable source shots remain useful when a brand needs later cutdowns, ads, retailer edits, or a revised sequence. |
| 3D product animation | 4 | Rendering covered product angles or internal ideas that are difficult to demonstrate clearly with camera footage alone. |
| Complete vertical social video | 3 | 9:16 work was treated as its own composition rather than a promise that every landscape shot would crop cleanly. |
Thirty of the 33 videos were horizontal and three were vertical. The shortest file was 6.0 seconds, the median was 37.9 seconds, and the longest complete collection film was 186.6 seconds. These numbers describe the sample; they do not prescribe an ideal duration.
What the still-image sets add
Sets, not isolated hero images
The 46 photographs came from six product groups. The useful planning unit was therefore a coordinated set: clean product form, details, scale, use context, packaging, and graphic-ready frames.
Marketplace and studio work overlap
Eleven files were finished Amazon listing-image examples, while the wider studio sets supplied the clean product views and detail evidence that marketplace layouts need.
Material handling changes the shot plan
Transparent components, reflective packaging, textiles, wood, food context, and hardware each required different lighting and retouching decisions. A single generic shot list would not describe them accurately.
Channel copy should follow visible proof
Feature graphics work best when the underlying photograph genuinely shows the component, scale, surface, or use state. Copy zones should not be used to invent evidence that the source frame does not contain.
A practical deliverable map
Capture masters
Photographs, clean product angles, demonstrations, lifestyle actions, voice-free sequences, and B-roll should be recorded before channel-specific crops and text are locked.
Build channel derivatives
Amazon galleries, A+ modules, Shopify media, homepage motion, landscape video, 9:16 social edits, thumbnails, and ad cutdowns should be named as separate deliverables.
Preserve claim boundaries
Approved product facts and visible evidence should travel with the asset plan. Editors should know which measurements, accessories, benefits, and use states are confirmed.
Prepare web delivery separately
The 79 primary source files totaled about 8.51 GB. Their WebP and 1080p primary delivery counterparts totaled about 905 MB, an approximately 89% reduction before poster derivatives. Masters remain separate from website files.
Method and limitations
Counts came from the studio’s portfolio conversion manifest. Video width, height, and duration were read from the 33 optimized 1080p files with ffprobe. Roles were classified from the public filenames and reviewed project context: finished horizontal video, vertical social video, B-roll, or 3D animation.
The sample is deliberately narrow. It contains one recent intake, reflects work selected for publication, and does not measure briefs, revision counts, budgets, traffic, conversions, marketplace approvals, or client outcomes. Raw client files are not offered as a public download.
Use the note as a planning check
Before a sample moves to the studio, list the capture masters, channel derivatives, approved claims, review authority, and web-delivery versions separately. That prevents a short homepage clip, a vertical social edit, and a complete product demonstration from being treated as interchangeable files.

