supabase db reset failed to send batch 08P01: UTF-16 Fix
supabase db reset fails with 'failed to send batch: ERROR: insufficient data left in message (SQLSTATE 08P01)' when your seed.sql is saved as UTF-16. Convert it to UTF-8 and reset cleanly.
<!-- BRIEF SPEC (supabase-cli-v2-config-as-code) Variant: PROBLEM-SOLVER | Hook: BENEFIT-FIRST | FAQ: 4 | ~900-1400 words Cover style: BLUEPRINT (problem-solver) — deep blueprint-blue, white grid; line-art of a terminal window running supabase db reset with a seed.sql document schematic beside it. Different central shape from the branching article. No text. In-body images (1): before/after diagram of the seed.sql pipeline — UTF-16 file feeding into the CLI's batch sender failing vs UTF-8 file flowing into a successful reset. SERP Step 0: one thin Medium post and scattered GitHub issues (COPY FROM STDIN 42601, FK violations 23503) — no tutorial covers the full "failed to send batch" family plus the config.toml seed settings. Gap: encoding check + config triggers + verify loop in one place. --> Last updated: 2026-10-10 The fastest local Supabase loop is one command: supabase db reset rebuilds your database from migrations and reseeds it, so every feature branch starts from a known state. When that command dies on the seed step, your whole config-as-code workflow stalls — you cannot test migrations, you cannot onboard a teammate, and you end up hand-fixing a database that should be disposable. The good news is that the most common cause is a one-line fix: the CLI chokes when seed.sql is saved as UTF-16 instead of UTF-8. Convert the encoding and your reset loop is back. What the supabase db reset failed to send batch 08P01 error looks like The output looks like this — everything succeeds until the seeding step: $ supabase db reset Resetting local database... Recreating database... Initialising schema... Applying migration 20250104000000_create_initial_schema.sql... Applying migration 20250105225630_add_profiles.sql... Seeding data from supabase/seed.sql... failed to…