TL;DR
- Customily's print file output is the design at print resolution, positioned within the vendor's required print area, in a format the vendor accepts.
- What's in the file: the customer's typed text in chosen font/color, uploaded photos, any clipart/template elements, all flattened to a print-ready layer.
- DPI and color profile matter — most POD print needs 300 DPI; color profile varies by vendor/method (sRGB common; CMYK for some specialty methods).
- Positioning tied to the vendor's print zone — text or art outside the zone is silently clipped at production.
- Where it goes wrong: low-resolution photo uploads, fonts not embedded, transparency handling, color shifts on certain materials. Verify with test orders.
What's actually in a Customily print file
When a customer completes a personalization in Customily, the app produces a print-ready output containing the customer's design at the resolution and format the POD vendor's production system needs. The file typically contains: the customer's typed text rendered in the chosen font, color, and size; any uploaded photos at the chosen scale and position; any template/clipart elements the customer kept; everything composited and flattened into a print-ready layer aligned to the product's print zone. See POD print file specs guide for the broader spec context across vendors and Customily for Apparel Stores for the broader app fit.
DPI, color profile, format
| Spec | Typical print requirement | What to verify |
|---|---|---|
| Resolution / DPI | 300 DPI at print size for most POD methods (DTG, sublimation, vinyl) | Customily outputs at vendor's required DPI; customer uploads pass minimum at the chosen size |
| Color profile | sRGB common for digital print; CMYK for some specialty/screen-print methods | Color profile matches what the vendor's RIP expects to avoid color shift |
| File format | PNG (transparency-supported) or PDF most common; vendor-specific in some cases | Format matches vendor accept list |
| Print zone alignment | Design positioned within the vendor's print area for the product | Customily's print area exactly matches the vendor's spec — no off-zone overflow |
| Transparency handling | Transparent background for prints on colored garments | Background actually transparent, not white-pixel-filled |
Where print files go wrong
- Low-resolution customer uploads: customer uploads a 500×500 photo at print at 300 DPI → blurry print, support ticket. Set a minimum-resolution requirement on upload fields and warn the customer if their file falls below spec at the chosen size.
- Fonts not embedded: if your output is PDF, fonts must be embedded or text renders in a fallback font. Most personalizers embed by default; verify with a test order.
- Transparency handling on colored garments: prints on dark fabric need transparent backgrounds; a white-pixel background renders as a visible white box. Trial on a colored garment first.
- Color shift between sRGB and CMYK: if the vendor's RIP expects CMYK and you ship sRGB (or vice versa), color shifts on print. Confirm color profile with the vendor and configure Customily to match.
- Off-zone clipping: if Customily's configured print zone is larger than the vendor's actual production zone, design elements outside the actual zone are silently clipped at the vendor. Cross-check exactly.
- Print method mismatch: a file optimized for DTG may not work well on sublimation or vinyl. Different POD methods have different file expectations — verify per method.
How to verify your print pipeline
The only reliable verification is test orders placed through your live setup, fulfilled by the real POD vendor, with the actual product in your hand. Specifically:
- Test each vendor you fulfill through — vendor specs and behaviors differ.
- Test each product type — apparel vs mugs vs phone cases handle differently.
- Test each print method the vendor uses for your products — DTG, sublimation, vinyl, embroidery.
- Test edge cases: low-res photo uploads, very long text strings, multi-line text, transparent vs solid colored garments.
- Document the spec for each vendor/method/product combination so onboarding new products doesn't repeat the verification work.
Want vendor-agnostic print files?
Customily's POD integration is one model. PIMW Product Personalizer passes the customer's personalization data via Shopify line item properties, so your vendor (or in-house production) generates the print file from a documented spec — and you can switch vendors without changing personalizer. Free plan, no per-item fees.
Install PIMW Product Personalizer — Free Read line item properties for POD →Frequently asked questions
What does Customily's print file output actually contain?
The customer's design at print resolution, ready for the POD vendor's production system: text rendered in the chosen font/color/size, any uploaded photos at chosen scale and position, any template or clipart elements the customer kept, everything composited and flattened into a print-ready layer aligned to the product's print zone. The exact format (PNG, PDF, etc.) and color profile (sRGB, CMYK) vary by what the vendor accepts. Verify Customily's current output specs per vendor on the Shopify App Store listing.
What DPI does Customily output for POD print?
Most POD print methods (DTG, sublimation, vinyl) require 300 DPI at print size — meaning the design's resolution at the actual printed dimensions must be at least 300 dots per inch for clean output. Customily targets vendor-spec DPI on output; the upstream variable is customer-uploaded photos. If a customer uploads a 500×500 photo and prints it at 10"×10", that's 50 DPI at print and the result is blurry. Set minimum-resolution requirements on photo upload fields and warn customers before they finalize designs that fall below spec at the chosen size.
How does Customily handle color for POD print?
Color profile depends on what the vendor's RIP (raster image processor) expects. sRGB is common for digital-print methods like DTG; some specialty or screen-print methods expect CMYK. Color profile mismatches cause color shifts at print — what the customer saw on screen isn't what arrives in the package. Confirm color profile with each vendor you fulfill through, configure Customily accordingly, and verify with test orders. This is one of the most common 'why doesn't the print match the preview' issues and is fixable upfront with spec alignment.
What about transparency on colored garments?
Prints on dark or colored garments need transparent backgrounds — a print file with white-pixel background renders as a visible white box around the design on a dark garment, which looks like a defect. Verify Customily's output has true transparency (not white pixels) and confirm with a test order on a colored garment before going live. This is a quick visual check that catches a class of issues invisible in the customer-facing preview.
What is print zone alignment and why does it matter?
Each POD product has a print zone — the area on the garment where decoration can actually be applied. Designs positioned outside the zone are silently clipped at production: the customer sees their design in the preview, the print file flows to the vendor, the vendor clips off the parts outside their zone, and the customer gets a partial design. The fix is to ensure Customily's configured print zone for each product exactly matches the vendor's actual production zone. Cross-check the vendor's spec against Customily's setup; verify with test orders that use the full print area.
How should I verify my Customily print pipeline is correct?
Test orders through your live setup, fulfilled by the real vendor, with the actual product in your hand. Specifically: test each vendor you fulfill through (specs differ), each product type (apparel vs mugs vs phone cases), each print method (DTG vs sublimation vs vinyl vs embroidery), and edge cases (low-res photo uploads, very long text, multi-line text, transparent vs colored garments). Document the spec for each vendor/method/product combination as a runbook so new product onboarding doesn't repeat the verification work. Print files are the part of personalizers that's easiest to assume-correct and hardest to fix after orders ship wrong.
Is PIMW Product Personalizer free to install?
Yes. PIMW Product Personalizer is free to install from the Shopify App Store. The Free plan includes 1 personalizer template on up to 2 personalized products; paid plans (Basic $7.99, Pro $13.99, Unlimited $24.99 per month, each with a 3-day free trial) raise the template, step, and product assignment limits. Every plan includes unlimited custom orders with no per-order fees. There is no upfront fee and no credit card required to install.
How long does PIMW Product Personalizer take to set up?
Most stores set up their first personalized product in under 15 minutes. The Shopify App Store install takes about 60 seconds; adding text fields, photo upload, color swatches, and live preview to a product takes 5-10 minutes. Catalog-wide rollout (50+ products) uses bulk-apply templates and typically takes 30-60 minutes total.
Does PIMW Product Personalizer work with Shopify Basic, Shopify, Advanced, and Shopify Plus?
Yes. PIMW Product Personalizer works on every Shopify plan including Basic, Shopify, Advanced, Plus, and Shopify Starter. The core personalization fields, live preview, and order capture work on every tier.
Does PIMW Product Personalizer slow down my Shopify store?
No. PIMW Product Personalizer uses Shopify's storefront block architecture, which loads only on personalized product pages and doesn't add render-blocking scripts site-wide.
Does PIMW Product Personalizer work with Printful, Printify, Gelato, and other POD partners?
Yes. PIMW Product Personalizer writes the customer's personalization to standard Shopify line item properties, which Printful, Printify, Gelato, and other major print-on-demand apps read. The data flows through Shopify's standard order pipeline, so any partner that reads line-item properties (which all major POD apps do) receives it with the order.
Does PIMW Product Personalizer support Shopify Markets, multiple currencies, and multiple languages?
Yes. Field labels translate per language, upcharge prices can be set per currency, and the personalizer fully supports right-to-left languages including Arabic and Hebrew. The personalizer also handles Unicode for Cyrillic, CJK (Chinese/Japanese/Korean), Greek, and accented Latin characters with appropriate font fallback.