Fixes for iPhone and iPad: your photo is kept while the try-on window is open, and Save works even when the share sheet does not open in time. The numeric size table now runs 32 to 62 instead of stopping at 44, so petite and plus-size shops can enter the sizes they sell. Recommended update.<\/p>","1.0.22":"
Adds a pause switch and a staff-only test mode, so you can trial the Try-On with your own team before showing it to customers. Optional \u2014 nothing changes unless you turn them on.<\/p>","1.0.21":"
Reliability release for the try-on window: a finished try-on is no longer lost to a temporary network hiccup, two browser tabs no longer cancel each other's paid try-on, and switching products always shows the right result. Recommended update.<\/p>","1.0.20":"
Maintenance: translations now ship as WordPress.org language packs (no bundled catalogs). Includes the 1.0.19 security & privacy hardening. Recommended update.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3631060,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3631060,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3631060,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3631060,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.21","1.0.22","1.0.24","1.0.25","1.0.28","1.0.30","1.0.33","1.0.34","1.0.35","1.0.36","1.0.38","1.0.39"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3631060,"resolution":"1","location":"assets","locale":"","width":2000,"height":1640},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3631060,"resolution":"2","location":"assets","locale":"","width":2000,"height":1640},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3629431,"resolution":"3","location":"assets","locale":"","width":2560,"height":1640},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3631060,"resolution":"4","location":"assets","locale":"","width":2560,"height":2900}},"screenshots":{"1":"The try-on result \u2014 the customer's own photo, wearing the product, generated by AI. A Before \/ After toggle sits above it, add-to-cart and save below.","2":"AI Size Advisor \u2014 the short quiz runs while the try-on generates, so the size recommendation is ready together with the result.","3":"WooCommerce product page \u2014 the \"Try It On\" button in the standard product layout, above Add to cart.","4":"Admin settings \u2014 environment health checks, button visibility, and the Size Advisor \/ Eye Advisor configuration."}},"plugin_section":[],"plugin_tags":[2353,282,7097,148223,286],"plugin_category":[45],"plugin_contributors":[273967],"plugin_business_model":[],"class_list":["post-306734","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-ecommerce","plugin_tags-fashion","plugin_tags-virtual-try-on","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-piezak","plugin_committers-piezak"],"banners":{"banner":"https:\/\/ps.w.org\/anytry-ai-virtual-try-on-for-woocommerce\/assets\/banner-772x250.png?rev=3631060","banner_2x":"https:\/\/ps.w.org\/anytry-ai-virtual-try-on-for-woocommerce\/assets\/banner-1544x500.png?rev=3631060","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/anytry-ai-virtual-try-on-for-woocommerce\/assets\/icon-128x128.png?rev=3631060","icon_2x":"https:\/\/ps.w.org\/anytry-ai-virtual-try-on-for-woocommerce\/assets\/icon-256x256.png?rev=3631060","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/anytry-ai-virtual-try-on-for-woocommerce\/assets\/screenshot-1.png?rev=3631060","caption":"The try-on result \u2014 the customer's own photo, wearing the product, generated by AI. A Before \/ After toggle sits above it, add-to-cart and save below."},{"src":"https:\/\/ps.w.org\/anytry-ai-virtual-try-on-for-woocommerce\/assets\/screenshot-2.png?rev=3631060","caption":"AI Size Advisor \u2014 the short quiz runs while the try-on generates, so the size recommendation is ready together with the result."},{"src":"https:\/\/ps.w.org\/anytry-ai-virtual-try-on-for-woocommerce\/assets\/screenshot-3.png?rev=3629431","caption":"WooCommerce product page \u2014 the \"Try It On\" button in the standard product layout, above Add to cart."},{"src":"https:\/\/ps.w.org\/anytry-ai-virtual-try-on-for-woocommerce\/assets\/screenshot-4.png?rev=3631060","caption":"Admin settings \u2014 environment health checks, button visibility, and the Size Advisor \/ Eye Advisor configuration."}],"raw_content":"\n
AnyTry is an AI-powered virtual try-on system that lets your customers see how they'll look wearing your products before they buy. The plugin integrates directly with WooCommerce product pages, adding a \"Try On\" button that uses cutting-edge generative AI.<\/p>\n\n
This plugin connects to the AnyTry API (https:\/\/api.anytry.ai) to generate virtual try-on images using generative AI. Using the plugin requires an AnyTry account (a free trial is available from the plugin settings screen).<\/p>\n\n
What the plugin uses the AnyTry API for:<\/strong><\/p>\n\n The Try-On feature works whether or not analytics is enabled. Enable analytics at WooCommerce \u2192 AnyTry AI \u2192 \"Send analytics & conversion events\".<\/p>\n\n What is sent to the AnyTry API:<\/strong><\/p>\n\n When the data is sent:<\/strong><\/p>\n\n Cookies (server-set, persistent):<\/strong><\/p>\n\n Persistent browser storage (localStorage):<\/strong><\/p>\n\n Ephemeral per-tab storage (sessionStorage):<\/strong><\/p>\n\n These stores are scoped to the current browser tab. They support the Try-On interface and, when analytics consent is enabled, retry failed analytics events. A photo stored here powers the local before\/after toggle; when the widget restores an earlier try-on (for example after a page reload), that stored photo can also be sent with a Size Advisor request the customer initiates. Quiz answers may likewise be reused in such a request. The photo is bound to its own try-on job; another job's upload is not used as a fallback.<\/p>\n\n Persistent browser storage (IndexedDB):<\/strong><\/p>\n\n Generated results are cached in the visitor's browser for local display. An older installation may also retain an uploaded-photo cache, described below. Clearing the site's browser data removes these caches.<\/p>\n\n Analytics consent:<\/strong><\/p>\n\n The plugin does NOT send analytics or conversion-attribution events by default. Enable them at WooCommerce \u2192 AnyTry AI \u2192 \"Send analytics & conversion events\". The Try-On image generation itself works whether or not this is enabled \u2014 only the conversion-attribution dashboard in the AnyTry Portal depends on this opt-in.<\/p>\n\n When analytics is enabled and a tracking token is available, the widget checks the current merchant setting and the site's Optional Google Fonts (default OFF):<\/strong><\/p>\n\n By default the plugin uses system-sans typography and makes NO third-party font request \u2014 the AnyTry API is the only external service it contacts. An internal Customer and product images are sent to AnyTry and the selected AI providers, including Google, for processing. Uploaded images, generated results, browser caches and Size Advisor data have separate lifecycles. Closing the widget does not trigger immediate deletion of every copy. Server cleanup depends on deployed retention settings and scheduled cleanup; this plugin does not enforce a five-minute deletion deadline. Entered and estimated measurements and analytics records may remain after image cleanup. Minimal removal markers (try-on identifier, removal time and terminal state; no photos or access tokens) are stored in the browser to synchronize removal across tabs. The widget honors them for up to 25 hours and removes expired markers on the next successful synchronization. Clearing all site data also removes these markers; older open tabs may need a reload to use the new synchronization.<\/p>\n\n This service is provided by AnyTry. By using the plugin, customers agree to the AnyTry Terms of Service and Privacy Policy:<\/p>\n\n Key Features:<\/strong><\/p>\n\n How It Works:<\/strong><\/p>\n\n SaaS Model:<\/strong> This plugin connects to the AnyTry API<\/a> for AI processing. An API key is required (free trial available). See Terms of Service<\/a> and Privacy Policy<\/a>.<\/p>\n\n The plugin ships its full unminified sources \u2014 Third-party code: The widget sends photos to AnyTry for processing by the selected AI providers, including Google. Browser images, server images and Size Advisor records have separate lifecycles. Closing the fitting room does not immediately erase every copy. See the privacy information above and the service Privacy Policy for processing details.<\/p><\/dd>\n Most try-ons finish in 15\u201320 seconds. The plugin does not paste the garment onto the photo \u2014 it generates an entirely new image with generative AI, which is a genuinely heavy computation. The widget shows a live progress estimate while it works, and the customer can minimise the window and keep browsing; the finished result is picked up as soon as it is ready.<\/p><\/dd>\n Best results come from full-body photos with good lighting on a plain background.<\/p><\/dd>\n The plugin stores its WooCommerce configuration options (API key, button style, size advisor mode, etc.) and a small amount of WooCommerce order metadata for conversion attribution. No customer photos are ever stored on your site. AI processing and the analytics reports themselves are handled by the AnyTry cloud service; on your site the plugin keeps only the bookkeeping records described below, which let it deliver those reports reliably.<\/p>\n\n Version 1.0.36 stores each new purchase, cancellation or refund as a complete operation before background delivery. A confirmed purchase snapshot is retained while the order exists so later order edits do not replace its recorded facts. Delivered cancellation and refund payloads become eligible for minimization after 30 days; undelivered operations and incomplete refund groups after 90 days. Ready purchases held because analytics consent is off follow the existing 14-day default. Minimal records remain to prevent duplicate operations and distinguish confirmed delivery from unconfirmed expiry. After permanent order deletion is verified in both WooCommerce stores, a maintenance pass removes the purchase facts from records older than 24 hours. Moving an order to trash does not do this. The personal-data eraser removes per-order records. Cleanup requires the scheduler and database to be available.<\/p>\n\n For older queued events and the other local records, the existing rules remain: Three small database tables are used for bookkeeping only. One prevents the same cancellation being reported twice; these records have no age limit. The outbox records purchase, refund and cancellation work before it is sent to AnyTry in the background, so temporary network or server problems can be retried. Delivered purchase and return entries become eligible for removal 30 days after delivery. Queued purchase and return entries in the ready phase age out at 90 days from admission once due; failed or quarantined purchase and return entries become eligible for removal at 90 days from admission. Return entries are only removed after their refund accounting has been preserved; if that repair cannot complete, they remain without an age limit. Two kinds are removed sooner, by default after 14 days from admission: ready purchases while analytics consent is off, and ready deferred refunds whose readable order shows no AnyTry activity and has no purchase still owed. Unresolved refund reservations and pending refund or attribution receipts have no age limit. Legacy staged purchases can remain without an age limit, including while held for an unknown or different account; an unreadable legacy order's staged batch can be retired after 90 days when recovery runs. New purchases keep one fixed declaration of the products and try-on identities being reported, so interrupted recording resumes the same purchase. After publication, this declaration retains product and order-line identifiers and attribution, without product names or amounts. It has no age limit while the order remains; after the order is permanently deleted and its absence is verified in both WooCommerce stores, a later maintenance pass reduces a declaration older than 24 hours to a minimal order and ownership marker. Moving an order to trash is not permanent deletion. Pending cancellation records retain a snapshot of the order lines and attribution; resolved reports also keep their exact outgoing content until acknowledged. Purchase declarations awaiting publication and cancellation work stop automatic attempts after 12 failures or when due work reaches 90 days, and remain for operator review. Consent or account holds consume no attempts. These new records are not removed merely because they are old. An acknowledged cancellation leaves the duplicate-prevention record; interrupted cleanup is retried. Orphaned cancellation content is diagnosed separately and retained for review. The outbox also keeps permanent per-order refund ledgers and ownership records: they preserve refund amounts and coverage, order and refund ids, the owner's key fingerprint and, when known, account id, without customer names, contact details or photos. Key-to-account mappings are kept as options containing key fingerprints, account ids and validation times, without order or customer data; they remain until uninstall because other orders may still refer to them. An option also registers purchases that could not be queued: it keeps at most 200 outstanding orders and sheds the oldest on overflow \u2014 except an entry whose ownership could not yet be recorded (for example during a database outage), which is kept until it can be, and stops retrying after 24 unsuccessful recovery attempts; account holds use no attempts and have no age limit. The third table, submit-answer escrow, briefly keeps hashes, a job id, an encrypted job access token and a small status response so the answer to one try-on submission can be recovered; it stores no photos and becomes eligible for hourly cleanup 25 hours after its last update. Cleanup depends on the background scheduler and database being available. Changing to another API key of the same AnyTry account changes nothing about ownership or delivery. Purchase, refund and cancellation data known to belong to a different account is never sent to the new account and follows the same retention rule as any undelivered entry of its kind, including the kinds with no age limit. When account ownership cannot be verified, history remains held: two known different accounts on one legacy order cannot be resolved automatically or by CLI assertion, an unmapped legacy key remains held until mapped, and a read failure before an ownership candidate is verified leaves unknown provenance that never resolves automatically; an operator may explicitly assert ownership of genuinely unknown history through the CLI, but cannot override known conflicting accounts, and during a storage outage the refused-purchase register may exceed its usual 200-order limit because entries whose ownership cannot be preserved are retained. All three tables and the key-to-account mappings are removed on uninstall. The plugin's WordPress personal-data eraser removes the shopper's per-order rows, including purchase declarations, permanent refund and ownership records, pending and acknowledged cancellation records, refused-purchase references and order metadata, regardless of WooCommerce's \"remove order data\" setting; shared key-to-account mappings are retained until uninstall. One non-personal marker (a timestamp) is retained per erased order so erased analytics cannot be silently re-created and re-sent.<\/p><\/dd>\n\n
api.anytry.ai<\/code> or an *.anytry.ai<\/code> subdomain.<\/li>\n\n
\/api\/v2\/commerce\/evidence<\/code>; older queued events keep their previous delivery path \u2014 only when analytics consent is enabled<\/strong>.<\/li>\n\n
\n
anytry_session<\/code> cookie (90 days) \u2014 stores the random session ID and the list of product IDs the visitor has tried on, used to attribute orders to try-on sessions for the conversion dashboard. Set only when analytics consent is enabled.<\/strong><\/li>\nanytry_tried<\/code> cookie (90 days) \u2014 stores a fallback list of tried product IDs for cases where anytry_session<\/code> is unavailable (third-party cookie blockers, REST checkout flows). Set only when analytics consent is enabled.<\/strong><\/li>\nanytry_legal_accepted_v2<\/code> cookie (1 year) \u2014 remembers that the customer has accepted the Try-On legal\/age-consent overlay so they are not asked again on every page. Set ONLY after the customer clicks \"Accept\" on the legal overlay. Not used for any analytics or attribution.<\/li>\n<\/ul>\n\n\n
anytry_lang<\/code> \u2014 the language chosen in the widget, used to restore that choice on later visits.<\/li>\nanytry_legal_accepted_v2<\/code> \u2014 mirror of the consent cookie above, same purpose, same trigger. No analytics or attribution use.<\/li>\nanytry_tried<\/code> \u2014 client-side mirror of the anytry_tried<\/code> cookie value, used when third-party cookies are blocked. Written only when analytics consent is enabled.<\/strong><\/li>\nanytry_tried_products<\/code> \u2014 same purpose as anytry_tried<\/code> but stored in a structured per-product map; used by the admin Conversions tab to attribute orders to try-on sessions. Written only when analytics consent is enabled.<\/strong><\/li>\nanytry_canonical_session_id<\/code> \u2014 a random sess_*<\/code> identifier kept across reloads so the API can JOIN a try-on generation event to a later purchase event for conversion attribution. Persisted only when analytics consent is enabled.<\/strong> When consent is off, an ephemeral id is held in memory for the current page only and never written to localStorage.<\/li>\nanytry_active_jobs<\/code> \u2014 registry of try-on jobs and their recovery metadata, used to resume work and restore completed results after a page reload. Completed entries can remain until the customer removes them. On widget startup, entries older than one hour are discarded; this is a cleanup check, not a background deletion timer while the page is closed. Removing a still-running job can retain a minimal status handle until the server confirms completion\/failure or the one-hour limit is checked. Removing a completed job retains only its job identifier, dismissal time and removal flags for up to one hour, checked on startup, so open or resumed copies can remove the same result. This removal record contains no image or job token and does not occupy an active try-on slot. Not used for analytics or attribution.<\/li>\n<\/ul>\n\n\n
anytry_before_<jobId><\/code> \u2014 a compressed copy of that job's uploaded photo, kept for the \"before \/ after\" toggle and a customer-initiated repeat Size Advisor analysis after a reload. If this copy is unavailable, the widget keeps the generated result but does not substitute another photo.<\/li>\nanytry_result_<jobId><\/code> \u2014 the generated result image data URL, used so the same result re-renders instantly when the customer reopens the modal in the same tab.<\/li>\n_anytry_result_cache_order<\/code> \u2014 job identifiers in cache order, used to evict older result images when the per-tab image cache reaches its limit.<\/li>\nanytry_feedback_state<\/code> \u2014 whether the customer already rated \ud83d\udc4d \/ \ud83d\udc4e the current result.<\/li>\nanytry_quiz_user_height<\/code>, anytry_quiz_user_weight<\/code>, anytry_quiz_usual_size<\/code>, anytry_quiz_skipped<\/code> \u2014 Size Advisor quiz answers, kept so the customer doesn't have to re-enter them while comparing multiple try-ons.<\/li>\nanytry_size_recommendation<\/code>, anytry_size_<photoHash><\/code> and anytry_size_<photoHash>_p<productId><\/code> \u2014 cached Size Advisor responses, which may include estimated body measurements and recommended sizes, used to restore the recommendation for the photo and product.<\/li>\nanytry_tab_id<\/code> \u2014 a random identifier used to keep track of which browser tab owns an active try-on job after a reload.<\/li>\nanytry_pending_submit<\/code> \u2014 pending request identifiers, timestamps, recovery credentials, intent and product metadata. With submission recovery enabled, these records let WordPress recover an accepted job after a lost response without starting a second try-on. Recovery checks discard expired records after 25 hours; dismissed requests are marked so they are not restored as wanted. Legacy records use the older short cancellation path.<\/li>\nanytry_sw_blocks_sse<\/code> \u2014 internal counter the plugin uses to detect a Service Worker that's blocking real-time updates, so it can transparently fall back to the same-origin SSE proxy on the next try-on.<\/li>\nanytry_pending_events_v1<\/code> \u2014 up to 20 failed critical analytics events, including their product, job and session identifiers. With current analytics consent, the plugin retries them at the AnyTry API on a later page view in the same tab. A refusal received by the widget or disabled analytics clears this queue and prevents new retries on that page.<\/li>\n<\/ul>\n\n\n
anytry_cache<\/code> \u2192 object store photos<\/code> \u2014 legacy uploaded-photo cache. The current widget does not write new uploads here or use this global cache for before\/after comparison or repeat Size Advisor requests. Existing cache cleanup remains in place.<\/li>\nanytry_results<\/code> \u2192 object store images<\/code> \u2014 the data URL of generated result images keyed by job ID, so revisiting a recently-generated try-on renders instantly.<\/li>\n<\/ul>\n\nanytry_allow_session_cookie<\/code> consent filter through WordPress once per page view, before sending or retrying browser analytics. It reuses that result for the rest of the page. CMP integrations must implement that filter; the plugin does not automatically detect every consent manager. An explicit refusal or disabled analytics clears the browser's attribution cookies, attribution storage and pending-event queue. A failed or unrecognized consent check clears the pending-event queue and stops browser analytics for that page, while preserving existing attribution and session identity. Try-On and Size Advisor remain available. This does not recall requests already transmitted or erase historical order records.<\/p>\n\nanytry_load_google_font<\/code> option (OFF by default, with no user-facing control) would, if enabled, request the Outfit web font from Google Fonts (https:\/\/fonts.googleapis.com) on the storefront and the AnyTry admin Settings page; it stays off in a standard install.<\/p>\n\n\n
\n
\n
\n
Configuration<\/h3>\n\n
\n
Requirements<\/h3>\n\n
\n
Source code & build<\/h3>\n\n
src\/js\/anytry.js<\/code>, src\/css\/anytry.css<\/code> and src\/css\/anytry-admin.css<\/code> \u2014 alongside the minified runtime in assets\/<\/code>. The two small admin scripts keep their unminified sources in assets\/<\/code> next to the minified files. Minification is done with esbuild on Node.js 18+ via the minify_wp.js<\/code> build script.<\/p>\n\nassets\/js\/heic2any.min.js<\/code> is a prebuilt bundle of heic2any 0.0.4 (MIT) that embeds gifshot (MIT) and libheif (LGPL-3.0-or-later). Full attribution, licence texts and the corresponding-source offer are in THIRD-PARTY-NOTICES.txt<\/code> in the plugin folder. It converts iPhone HEIC photos to JPEG in the browser, loads only when the customer picks an HEIC file, and can be turned off with the \"iPhone HEIC support\" toggle in WooCommerce \u2192 AnyTry AI.<\/p>\n\n\n\n
\n
Are customer photos safe?<\/h3><\/dt>\n
How long does a try-on take?<\/h3><\/dt>\n
What kind of photos should customers upload?<\/h3><\/dt>\n
Does this plugin store any data locally?<\/h3><\/dt>\n