In short: Val Town announced on November 10, 2026 that it is winding down. New signups and upgrades stopped that day, code becomes read-only on December 10, 2026, and everything else, including running vals, SQLite and blob storage, stops on January 10, 2027. If you have HTTP endpoints or cron jobs there, the safe plan is to copy the code into a Git repository now, move each cron to a scheduler that runs in UTC the same way, keep your own "last run" checkpoint, and only then point your *.val.run URLs at the new home.
The dates that actually matter
The official wind-down post by Val Town's founder lists four dates. Here is what each one means in practice:
- November 10, 2026: new signups and plan upgrades closed. Billing was paused the same day and existing subscriptions keep working for free; annual prepaid plans get a partial refund.
- December 10, 2026: read-only mode. You can no longer edit code, and this is also the last day to add or change
val.runredirects. Read-only mode does not include SQLite and blob storage, so data stays reachable a bit longer. - January 10, 2027: all other services end. Your vals stop answering HTTP requests and your crons stop firing.
- February 1, 2027: Val Town plans to open-source the platform.
The practical takeaway: December 10 is your real deadline for anything that needs editing, such as adding an export endpoint for your database or setting redirects. January 10 is when users notice.
Step 1: List what you have and decide what to keep
Val Town's own migration guide suggests starting by deciding which vals are worth moving at all. Many accounts are full of one-off experiments. For each val you keep, write down four things before touching any code:
- Trigger type: HTTP, cron, email, or plain script. Vals with a trigger must export a function (the default export when there are several), so the exported function is your entry point.
- Dependencies:
npm:imports,esm.townimports of other vals, and Val Town standard library helpers such as blob, email or SQLite. - Data: whether it uses its own SQLite database or the older account-global one, and which blob keys it reads and writes.
- Public surface: its
val.runURL or custom domain, and any webhook provider that calls it.
Val Town also publishes a ready-made prompt for doing this inventory with an AI coding agent through its plugin or MCP server. It asks the agent to list your vals, help pick a platform and propose a plan for you to approve, which is a reasonable way to handle a large account. If you only have a handful of vals, doing it by hand takes less time than setting that up.
Step 2: Get the code into Git
The vt CLI (installed with Deno: deno install -grAf jsr:@valtown/vt) can vt clone a val into a local folder, which is the quickest way to get plain files you can commit. Val Town's docs now recommend the plugin or MCP server over the CLI for most agent work, but for a straight copy, the CLI is enough.
Val Town's GitHub guide adds a few rules worth following even if you migrate by hand:
- Copy every val your app imports through
esm.towninto the project and switch to relative imports. Bundling a remote URL does not make the app independent of Val Town, and those URLs will stop resolving. - Keep private vals in a private repository. If visibility is unclear, start private.
- Add a
.gitignorebefore the first commit and leave out env values,.envfiles, database and blob exports, and logs. Ignoring a file later does not remove it from history. - Write a short README with the live URL, how to run and deploy, and the names (not values) of the environment variables.
One more reason not to just move the Deno code as-is: Val Town's migration guide notes that Val Town runs on Deno and links Deno's own announcement about winding down, saying core maintainers will not support Deno beyond October 2027. Val Town recommends moving to Node, Bun, or a provider runtime such as Cloudflare Workers or Vercel Functions.
Step 3: Pick a destination
Val Town's "Where to migrate" page compares providers by built-in features. Cloudflare is the only one ticked for every column (website, SQLite, blob, cron, email, access, AI and functions), and the team says it moved its own blog and docs there. Vercel and Netlify cover website, blob, cron, access and AI but not SQLite or email. Render covers website and cron. The table below focuses on the part that breaks most often in these moves: scheduled jobs.
| Destination | Where a cron val goes | Timezone | Gotchas noted in Val Town's guides | Built-in SQLite / blob |
|---|---|---|---|---|
| Cloudflare | Worker scheduled() handler + triggers.crons in Wrangler config |
UTC, like Val Town | Last-run time is not passed in; store it yourself. Use Queues or Workflows for long multi-step jobs. | D1 / R2 |
| Vercel | Vercel Schedules (currently beta) with @vercel/schedules |
Set per schedule (example uses UTC) | Hobby plan has a 15-minute minimum interval and timing jitter; schedules can also exist in preview deployments. | No SQLite / Vercel Blob |
| Render | Cron job service in render.yaml |
UTC | Cron jobs are paid services; let failures exit non-zero; no lastRunAt supplied. |
Neither built in |
| Netlify | Scheduled Function with config.schedule |
UTC | Runs only on published deploys; 30-second scheduled execution limit; next_run is not the last run. |
No SQLite / Netlify Blobs |
For reference, Val Town's own Free plan allowed crons every 15 minutes and Pro every minute, so a Vercel Hobby project matches a former Free-plan cadence but not a one-minute Pro job.
Step 4: Move cron jobs without losing state
This is where I would spend the most care. On Val Town, a cron handler received an Interval object with lastRunAt, and many vals used it to fetch only "what's new since the last run". None of the destinations above hand you that value. If you drop it, the job either reprocesses everything on the first run or silently skips items.
I wrote a small port to check the pattern: a Cloudflare-style scheduled() handler that keeps lastRunAt and a per-item "done" marker in a key-value store (an in-memory stand-in for Workers KV or D1 so it runs locally on Node 22). The core logic:
async function runJob(env, scheduledTime) {
const last = await env.KV.get("lastRunAt");
const lastRunAt = last ? new Date(last) : undefined;
for (const it of items) {
if (lastRunAt && new Date(it.at) <= lastRunAt) continue;
if (await env.KV.get("done:" + it.id)) continue; // retry guard
send(it);
await env.KV.put("done:" + it.id, "1");
}
await env.KV.put("lastRunAt", new Date(scheduledTime).toISOString());
}
export default { async scheduled(event, env) { await runJob(env, event.scheduledTime); } };
Run against two items, then a simulated retry of the same tick, then a new item an hour later, it sent a1, a2 on the first run, nothing new on the retry, and only a3 on the third run. That is the behavior you want: the checkpoint moves forward only after the work is recorded, and a retried run cannot send twice. Val Town's guides make the same point for every destination: record processed IDs so a repeated run does not resend messages or duplicate charges.
Watch the UTC trap
Val Town evaluates cron expressions in UTC, and so do Cloudflare, Render and Netlify. If you copy an expression as-is, the time stays the same. If you rewrite it from memory in local time, it moves. For a job meant to run at 9:00 local time, the UTC expression is 0 0 * * * in Tokyo or Seoul, 0 14 * * * in New York during standard time, and 0 17 * * * in San Francisco during standard time. Also note that a Val Town "simple interval" such as "every two hours" is an elapsed interval, not a wall-clock schedule; the guides warn the two are not always equivalent.
Cut over in the right order
Every destination guide gives the same order: test the handler with disposable data, pause the Val Town cron, enable the new schedule, then watch for one real scheduled run and check its effects. A successful deploy does not prove the job ran. Netlify's guide also warns never to publish a job handler without its schedule or an auth check, because an ordinary function URL would let anyone trigger it.
Step 5: Copy SQLite and blob data
Val Town's Cloudflare guide exports SQLite by adding a temporary HTTP val that streams the tables as SQL, protected by a random bearer token you keep out of the code and URLs. Pause writes while exporting, since streaming pages is not a snapshot, and keep the downloaded file out of Git because it contains plaintext data. Because this needs a new val, do it before December 10, even though storage stays readable until January 10.
For blobs, the guide says to list keys with pagination, copy the actual bytes (not just download URLs), preserve keys and content types, and compare counts, sizes and hashes before switching. A failed or rate-limited listing does not mean the store is empty.
Step 6: Redirect val.run URLs last
Val Town lets you redirect any *.val.run endpoint to its new URL from the val's settings (HTTP section) or from account or org settings under Custom Domains. Redirects keep the path and query string by default. Two details matter: the val stops receiving requests as soon as a redirect is set, so add it only after the new app is verified; and many webhook providers do not follow redirects, so update webhook URLs with each provider directly. You can edit redirects until December 10, 2026, when they become permanent. Custom domains are not covered by this; change their DNS at your domain provider.
Editor's note
Who this is for: anyone with HTTP vals, cron vals or stored data on Val Town, especially small automations (digests, webhooks, bots) that nobody has looked at in months. Less relevant: if you only used Val Town for throwaway scripts, cloning the few you like is enough.
Gotchas I'd check first: lost lastRunAt state (first run reprocesses everything); local-time rewrites of UTC cron expressions; leftover esm.town imports that break after shutdown (search your built output for esm.town and .val.run); Deno-only APIs that do not exist in Workers or Node; and webhooks that ignore redirects.
Common errors and fixes: a migrated cron "doesn't run" on Netlify because the deploy is not published, or on Vercel because the schedule exists only in a preview; a job runs twice after a retry because there is no processed-ID record; a redirect "breaks" a working val because it was set before the new app was live.
FAQ
Will my vals stop working on December 10?
No. December 10, 2026 makes code read-only and locks redirects. Vals keep running until January 10, 2027, and SQLite and blob storage are not part of the December read-only change.
Do I have to keep paying until then?
No. Val Town paused billing on November 10 and keeps existing subscriptions running for free; annual prepaid plans get a partial refund.
Which platform is closest to Val Town?
By Val Town's own feature table, Cloudflare, which has built-in equivalents for websites, SQLite (D1), blob (R2), cron, email and access. Vercel is the next closest if you do not need SQLite or email.
Related on lightmind24: Google Opal Shuts Down Nov 17: Back Up and Move Workflows · AWS Emulator Tutorial: Let Coding Agents Test AWS Locally · Agent Skills: One SKILL.md for Claude Code, Cursor, Copilot
Move the crons first and the redirects last, and you will have a quiet January 10.
Screenshots: see the official wind-down timeline, provider table, cron docs and Cloudflare cron guide, plus my own migration map, at the end of this post. Images: Val Town blog and docs.val.town, and lightmind24 own summary table.
Last verified: 2026-11-12
Sources: Val Town blog: Val Town is winding down (Nov 10, 2026) · Val Town migration guide · Where to migrate · Store code on GitHub · Redirecting val.run URLs · Cloudflare: migrate crons · Vercel: migrate crons · Render: migrate jobs · Netlify: migrate crons · Cloudflare: migrate SQLite · Val Town cron docs · Val Town pricing
lightmind24 is an independent review site, not affiliated with Val Town, Cloudflare, Vercel, Render or Netlify.
댓글
댓글 쓰기