| 开发者 | gopalbogati |
|---|---|
| 更新时间 | 2026年11月2日 13:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[wearlook] to any page or post with a featured image, or point it at any media-library image: [wearlook image="123"][wearlook] shortcode (uses the featured image) or [wearlook image="123"].Yes. Under Settings, Virtual Try-On, set "Show the button on" to "Only products recognised as clothing" for a hands-off setup, or pick the exact categories. Choosing a category includes everything beneath it. If a garment with an unusual name is missed, set its garment type under Product data, Advanced and the button appears.
It reads the product name, then its categories, for garment words such as jeans, shorts, skirt, dress or jacket, and uses the last one it finds: a "jean jacket" is a jacket, "polo shorts" are shorts. Sleeve lengths are ignored, so "short sleeve tee" stays a top. Each product's edit screen shows what was detected, and you can override it. Developers can add words in other languages with the wearlook_garment_keywords filter.
No. It works on any WordPress site via the [wearlook] shortcode. If WooCommerce is active, product pages get the button automatically.
Yes — the fitting room (automatic garment placement, drag/resize/rotate, download) is free and unlimited with no account. Only the optional photorealistic AI render uses a paid Wearlook Cloud subscription.
Not in the free fitting room — everything runs in the visitor's browser. A photo is only transmitted (over HTTPS, after explicit consent) when the visitor requests a premium AI render, and it is processed in memory, never stored.
Wearlook reads the visitor's photo, separates them from the background and measures their shoulders, then scales the garment to that measurement and hangs it from their shoulder line — so the same garment comes out larger on a close-up selfie and smaller on a full-length photo. The visitor can still fine-tune with drag and the size/rotate sliders. All of it runs in their browser; nothing is uploaded. If the photo is unusual — a busy background, or the head cropped out of frame — Wearlook says so to itself and falls back to a sensible fixed placement rather than guessing. The sliders are always there, and the Auto-fit button re-runs the automatic placement at any time, so no amount of dragging is a dead end. A new photo is always fitted automatically. Switching to another product image keeps the size and rotation already dialled in, so comparing two colourways on yourself stays one tap — press Auto-fit if you would rather start that image fresh.
Nothing on an ordinary product page. The pose model is only fetched the first time a shopper actually opens the fitting room and prepares a photo. That first use pulls about 17 MB: roughly 11 MB of MediaPipe runtime and 5.5 MB for the Pose Landmarker Lite model. The browser then caches both, so it is a one-off per shopper, and the files come from your own site rather than from Google. Measuring a photo takes about half a second the first time and under a tenth of a second after that. Shoppers on a slow connection can still place the garment by hand while it loads.
Yes. When Wearlook finds a person in the product photo it cuts the garment out of it — the model's head, arms and trousers are removed and only the garment is placed on the visitor. Flat-lay photos are used as they are, with the studio background knocked out.
Yes — [wearlook image="URL-or-attachment-ID"] works with any image in your media library. Pass several, separated by commas, to let the visitor choose: [wearlook image="12,13,14"].
Yes. When a product has more than one image, a thumbnail strip appears at the top of the try-on window. It offers the featured image, the product gallery, and the variation images of variable products — so a visitor can try the same garment in another colour or from another angle. Switching images keeps their uploaded photo and current fit, and the choice is validated server-side against that product's own images.
Yes. Under Settings → Virtual Try-On pick Google Gemini or FASHN.ai as the AI engine and paste your own key. Renders are billed to you directly by that provider, and the plugin adds no fee. Your key is stored in this site's database.
fal.ai is the most flexible: one key gives you a choice of purpose-built try-on models, so you can pick a cheaper or a higher-quality one from the settings dropdown. Google Gemini is usually the cheapest per image and the key takes a minute to create in Google AI Studio. FASHN.ai is purpose-built for garment try-on. Both are paid services. AI image generation is not included in Google's free API tier, so your Google account needs billing enabled; FASHN.ai is likewise a paid API. Expect roughly a few cents per render. Check each provider's current pricing before enabling renders on a busy store, and use the "AI renders per visitor per hour" limit to cap what visitors can spend on your behalf. If you would rather not pay anything, leave the engine on None — the fitting room stays free and unlimited.
Yes — every product has a "Disable virtual try-on" checkbox under Product data → Advanced.
Premium renders have a per-visitor hourly rate limit, configurable in settings (default: 10 per hour).
[wearlook image="12,13,14"].[wearlook] shortcode: featured image, attachment ID, or image URL.