I’ve previously evaluated enterprise-grade B2B virtual fitting software like Zeekit, alongside the traditional manual workaround of bracket shopping—ordering multiple sizes and returning the extras. While corporate B2B integrations offer slightly higher texture fidelity because they use high-resolution, multi-angle brand asset sheets, they are locked behind closed enterprise ecosystems and are only available on a tiny fraction of major retail sites. Size charts, on the other hand, fail to communicate how a fabric actually sits against a specific body shape. I opted for SnapPeach because it shifts the entire utility model to the consumer side, providing a universal, unrestrictive testing canvas that works on any independent boutique or legacy storefront instantly.
Congrats on launching! The 10-second claim is bold, how consistent is the output when the product photo is low quality or shot at a weird angle? Fashion sites vary wildly in image quality, so I'm curious how it handles the messy real world. Also smart choice making it a Chrome extension instead of yet another app; meeting people where they already shop makes a lot of sense.
@dennis_weijer1 Good question, and honestly it's the hard case. Render quality tracks the product photo - clean front-facing shots come out great, low-res or weird-angle ones are hit or miss. It holds your face and body well; the garment texture is what suffers when the source is bad. Making it smarter about picking the best product image on a page is next. Thanks for digging in.
@kunal_kakade1 Appreciate the honest answer. 'Render quality tracks the product photo' is a fair constraint, and auto-picking the best source image on a page sounds like the right next move. That's the kind of invisible improvement users will feel without knowing why. Good luck with the launch!
"processed in memory, never stored" is a good privacy line but it leaves one thing ambiguous: does that memory processing happen locally in the browser, or does the photo get sent to a server to generate the photoreal render and just not get persisted afterward? those are very different privacy claims even if the end result (nothing stored) is the same, and "never leaves your device" earlier in the pitch reads like the former.
@galdayan Fair catch, and the distinction genuinely matters - you're right to separate them.
Straight answer: the render is server-side, not local. The image models are far too heavy to run in the browser. When you hit try-on, your photo goes over an encrypted connection to our server, which forwards it to the image model to generate the render, returns the result, and discards all image data - held in memory only, never written to disk or a database.
So the precise claim is: your photos are never stored anywhere but your device (your render history stays local too). You're right that "never leaves your device" overstates it - the photo does travel in-flight during a render. That's on me for compressing it into a tagline. The full privacy policy walks the whole flow, Google's role included: snappeach.com/privacy.html
Net: nothing persists on our side, and the DB can't leak photos because it never holds them. But the honest version is "never stored off your device," not "never leaves it." Appreciate you holding the line on precision - privacy claims should be exact.
@kunal_kakade1 that's the answer I wanted, and correcting your own tagline in public instead of getting defensive says more about the product than the render speed does. going to actually try it on a few pieces I've been on the fence about.
The "fitting room on every store, works on any site" angle is way more useful to me than the single-retailer try-ons that only work where they are already built in. Day-one question: do I set my photo up once and it is reused across every site, or is it a fresh upload per garment — and can I save or share a render, or does it vanish when I leave the page? Trying to work out whether this fits a real "send the look to a friend before I buy" moment.
@leo404 Photo setup is once. You add up to 3 photos of yourself the first time. They're stored locally on your device and reused on every site - no re-upload per garment. You just hover a product and try it on.
Renders don't vanish. Each one saves to a local try-on history on your device, so you can go back to it later. And there's a share button that opens your native share sheet with the image, so you can send the look straight to a friend (Messages, WhatsApp, wherever) - or it copies the image to your clipboard as a fallback. So the "send it to a friend before I buy" moment is exactly what it's built for.
One thing worth knowing: your photos and your history live on your device, not our servers. So it's genuinely your image to share, not something we're holding onto.
Perfect — device-local history plus the native share sheet is exactly the day-one flow I was hoping for. One follow-up since it's all on-device: if I do the 3-photo setup on my phone and later shop from my laptop, do I redo setup there or does it carry over? Device-bound is totally fine, I just want to know whether my try-on history follows me across screens.
Being able to see how a piece looks on me before buying would honestly save me from so many returns. One thing I'd love is a side by side comparison mode where I can try two or three garments at once on the same page, makes it way easier to actually decide which one to go with.
@muammer116619 That's on the roadmap - multi-garment and outfit composition is exactly where I want to take it. One garment at a time for now. Would you want the same item in different colors side by side, or different items? Helps me prioritize.
Tried it on a couple of sites and it really did pop on me in like 15 seconds, which honestly surprised me. The fit looked pretty natural too, not stretched or warped like other try-on tools I have tested.
@tlin2096647 That's the target. Speed and no distortion are the two things I won't ship without. Thanks for trying it.
does it work on every site or do stores have to opt in first
@halitm7tv it works on every site