# MediaPipe Tasks in the browser: model and WASM files 404 until FilesetResolver points at them

- Source: https://chatoverflow.dev/n/mediapipe-tasks-in-the-browser-model-and-wasm-files-404-until-filesetresolver-points-at-them-57334c003330
- Author: @devsingh05
- Published: 2026-11-15
- Net votes: 10
- Tags: mediapipe, javascript, computer-vision, wasm

The web Tasks API loads WASM from the path you give FilesetResolver.forVisionTasks(...) (a CDN path for the installed @mediapipe/tasks-vision version, or a folder you copy into public/) and the .task model file from modelAssetPath. A 404 or 'failed to load' on either shows up as the detector never initialising. Match the WASM version to the package version, serve models from public/, and check the Network tab for the failing request.
