Skip to content
| Marketplace
Sign in
Visual Studio Code>Testing>SandForge: Realistic Data for Salesforce SandboxesNew to Visual Studio Code? Get it now.
SandForge: Realistic Data for Salesforce Sandboxes

SandForge: Realistic Data for Salesforce Sandboxes

Stephane Berthoz

|
45 installs
| (1) | Free
Fill an empty Salesforce sandbox, scratch org or Developer Edition with realistic test data: generate it from templates, no AI key needed, or clone a record and its graph from another org. Anonymize it, take a checkpoint of the org and rewind it later. Production guardrails on by default.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

SandForge: Realistic Data for Salesforce Sandboxes

Version TypeScript License Languages

Forge your Salesforce sandboxes. SandForge fills a sandbox, a scratch org or a Developer Edition org with realistic data: generated from a template, with no AI key, or cloned from a real record of another org, with production guardrails. One WebView UI, no Command Palette required.

A Forge clone from start to finish: a record Id, its relationship graph, the automation the target runs, a simulation, the gaps decided, the run, its results, and the removal of what it created

Website: sandforge.fr · en français


One empty org? Fill it in a minute

A new Developer Edition, a Trailhead playground or a fresh scratch org is all you need: Seed fills it with realistic records linked to one another, from a built-in template. No second org, no AI key, no field rule to write.

  1. Connect your org: click the SandForge icon in the Activity Bar. With no org registered yet, the launcher's Connect your first org card imports the orgs the Salesforce CLI already holds, or signs you in through your browser.
  2. Open Seed: with one sandbox, scratch org or Developer Edition org connected, the launcher's Fill <alias> with demo data opens Seed's template gallery on it, as Seed under Modules does.
  3. Pick a template: CRM Starter, marked Start here, comes first: accounts with their contacts, products priced in the standard price book, opportunities with their line items, and cases, about 300 records, which a Developer Edition's 5 MB of data storage holds. Click Use this, then check its record counts and the org, already selected.
  4. Click Start seeding. Nothing is written before; a seed that would not fit in the org's data storage, or would make its automation send more emails than the org has left today, is refused before its first record, and one past the storage offers the counts that fit.
  5. Take it back whenever you want: What this run created, on the results, or Earlier seeds, under the gallery, removes what the seed wrote.

Seed — the template gallery that fills an empty dev org, CRM Starter first

New here? The built-in Get Started walkthrough (Help → Welcome → "Get started with SandForge") takes you through connecting an org and filling it, then through Forge, inside VS Code.


Why switch from SFDMU or Data Loader?

  • No config file to author. Paste a record ID: BFS discovery walks the relationship graph for you and lookups are remapped on write (a record type the target does not have keeps its source Id, and the SandForge log names it). No export.json to hand-write, no field mapping to keep in step with the schema.
  • No mandatory CSV round-trip. Records move org to org over the API. CSV import is still there when you want it — one door in, not the only one.
  • Production Guard on by default. Forge refuses a production org as a target, and so do a Frozen Dataset load and Checkpoints, which does not even take a checkpoint of one; Seed, Sync, Autopilot and DataOps ask you before every write to one, and DELETE there is blocked outright. Nothing to switch on, nothing to remember.
  • Your existing SFDMU config comes with you, and what does not is named. The Migration module imports a real export.json into a Sync config: its objects, filters, keys, field and value mappings, with FieldMapping.csv and ValueMapping.csv. What Sync does not do as SFDMU would (master: false, a LIMIT, mockFields, a composite key, deletes in the source, add-ons) the import names before anything runs, and Open in Sync shows what each object does, a delete included, before the run; an object that useFieldMapping sends to another object is refused.

Side by side, with sources: SandForge, SFDMU and Data Loader compared.


Your first clone in 2 minutes

Two orgs, one holding real records (a UAT or partial-copy sandbox, say) and one to fill? Forge copies a record and everything around it from the first into the second.

  1. Connect your orgs: click the SandForge icon in the Activity Bar, open the org dropdown at the top of the launcher, choose New organization..., then Import from Salesforce CLI to pull in every org authenticated in the Salesforce CLI.
  2. Open Forge: click the flame icon in the sidebar, or run SandForge: Open Forge from the Command Palette.
  3. Paste a root record ID from the org you copy from into Record ID or Salesforce URL (an Account works well), and pick the org you fill as the target.
  4. Tune Depth, Records per object, and Anonymize PII on the same form, then click Discover Graph.
  5. Click Review & Execute toward the org you fill. Review says the run in one sentence and what is left to decide, over rows that open in place (Gaps, Plan, Automation and the others), with Simulate and Execute Forge in a column beside them, under a ribbon that names the org copied from and the org written into. IDs are remapped as the records are written; a record type with no active record type of the same API name on the target keeps its source Id, and the SandForge log names it.

Forge — live record preview, dependency estimate and PII detection


First steps, safely

  1. Clone into a Developer sandbox or a scratch org. Forge writes only to a sandbox, a scratch org or a Developer Edition org; it refuses a production org, and any org whose kind SandForge does not know.
  2. Simulate first. On Review, Simulate takes every record through the write stage and writes nothing. Its results say how many records a real run would insert, how many gaps it found against the target, and which record type the target would give the records that go in without one.
  3. Read the Automation and Gaps rows. Automation lists what the target runs on the records the run writes (flows, processes, workflow rules, Apex triggers, assignment and duplicate rules), marks what sends an email or a text message, says whether the target delivers those emails, and says what may refuse a removal of the run's records; a real run asks you in VS Code to confirm what fires on insert and update before it writes anything. Where the target's flows, processes and workflow rules test a bypass custom permission, Mute the target's automation for this run quiets them through the org's own bypass: the smallest permission sets holding it are assigned to you for the run and taken back as it ends, nothing is deactivated, and the run names what was muted and what still ran. It is refused on a production org. Gaps lists what the target would refuse or change in the rows, read from its metadata or found by a simulation or a rehearsal, each with the decisions it allows; the row counts the gaps that will refuse rows and have no decision yet.
  4. Emails and phone numbers are neutralized by default. Every email address is written under .invalid and every phone number as a fictional one, so that what the target's automation sends to them reaches no one, and a run asks first when the target would deliver its emails to anyone else, the records' owners or an address an alert names; past 10,000 distinct numbers in one run, a phone field is left empty instead, and Results counts it. Keep emails and phone numbers as they are turns that off.
  5. Rehearse when the target has validation rules or triggers. A simulation checks the rows against the target's fields; Rehearse has the target itself judge them, in calls it rolls back whole: every row when the run creates 200 or fewer, otherwise one row for each object, record type and set of filled fields. You confirm the calls it costs in VS Code first, and that confirmation names what a rollback cannot take back: platform events published immediately and callouts already made.
  6. Remove a run from Results. Remove the records this run created deletes them from the target, children before their parents, into its recycle bin; its confirmation lists what the target runs as they are deleted. Records the run linked to, which the target already held, are kept, and so is a record changed since the run unless you include it. The runs under Recent runs, and under Older runs once they leave that list, offer the same removal. Sweep first takes back with it what the target's automation made under the run's records, and lists what came late or is tied to nothing, kept unless you ask for it. Checkpoint first, beside Execute Forge on Review, goes further: the run takes a checkpoint of the objects it writes, and Rewind to before this run…, on its results, returns them to that moment.

Forge Review — the Gaps row with two gaps decided and one still refusing rows, above the Automation row

Forge simulation — nothing written, what a real run would insert, the gaps found and the emails and phone numbers it would neutralize


Modules

SandForge ships 15 modules in a single extension:

Module What it does
Forge Clone a record and its relationship graph between orgs, with BFS dependency discovery and automatic ID remapping, or the whole org with the ALL depth, or a sample of it that fits the target. Guide
Frozen Dataset Extract once, pseudonymize deterministically, replay identically after every sandbox refresh. Guide
Seed Fill an empty org from a built-in template in a minute, with no AI key; or generate data for the objects and field rules you choose (Faker, AI optional), import a CSV, or copy objects from another org. Test data for an Agentforce agent, from a scenario, with its test file. Guide
Checkpoints Keep the state of an org's data at a moment on this machine, and return the org to it: after a preview, Rewind deletes what was created since, gives back what was changed and brings back what was deleted — with View All Data and Modify All Data, whoever did it; the rewind itself can be undone. Never on a production org. Guide
Sync Source-to-target sync between orgs with field mapping, transforms, and conflict resolution against the target. Guide
Monitor API limits, jobs, storage, and health score read on open or refresh, with threshold alerts; Live Operations lists the runs under way, and one that left part of its work undone as Partial. Guide
Compare Metadata diff, permission set and profile presence, and five Organization settings, compared between two orgs. Guide
DataOps A snapshot of the records an anonymization writes over, and its restore; PII anonymization, data subject requests, a read-only data-quality scan, a cleanup of stale, orphaned and duplicate records through Production Guard, and the emptying of the objects you pick or of the whole org, with Undo. Guide
Automation Visual pipelines of backup, checkpoint, compare, precheck, notification, delay, condition, approval, sync, seed, anonymize and rewind steps, run by hand, on a cron schedule or a sandbox refresh while VS Code is open; a rewind step runs once confirmed with the org's alias, and can mute the org's automation through its own bypass. Guide
AI Assistant Chat, NL2SOQL, pipeline drafts and Seed field rules on your Anthropic key. Failed runs send their error for a fix unless sandforge.ai.errorResolution is off; known codes answer with AI off. Guide
Grappe A progress page, not an engine: once sandforge.grappe.enabled is on (off by default), a large Seed run reports there partition by partition, a large Sync one partition per object, and a large Autopilot run only its start and its end. Execution stays sequential. Guide
Migration Import existing SFDMU export.json files, with their FieldMapping.csv and ValueMapping.csv, into Sync configs run from Sync, naming first what Sync will not do as SFDMU would. Guide
Autopilot Copy whole objects from one org to another in dependency order, or the largest share of them the target's data storage holds, with the records they reference; emails and phone numbers neutralized by default, GDPR, CCPA, HIPAA or PCI-DSS masking optional. A run cannot be removed. Guide
Organizations Org registry with SF CLI import and tier-based safety coloring; when SandForge first opens a view in a window, expired sessions are refreshed through the sf CLI.
Reports Execution reports and success rates from your Forge and Sync run history, an audit trail of every run that writes to an org, and the data lineage of the records each run carried. Guide

Safety is on by default: Forge and a Frozen Dataset load refuse a Production org as a target, Checkpoints never takes a checkpoint of a Production org nor rewinds one, and for every other module Production Guard asks for confirmation before any write on a Production org and blocks DELETE there. Each of its decisions is recorded with the run it concerns, in Reports → Audit trail.


Which tool copies my data?

What the org needs Use Taking it back
Nothing copied: realistic records in an empty org Seed, from a template of its gallery What this run created, on the results, or Earlier seeds
One record and what hangs on it Forge Remove the records this run created, on the results or under Recent runs
Whole objects, filtered and mapped, as often as needed Sync Remove what this run created, on the results or the run's history entry
Whole objects in dependency order, in one go Autopilot A run cannot be removed; Rewind… to a checkpoint taken before it: Checkpoint first, on its review, takes one
The same set after every sandbox refresh Frozen Dataset Remove the records this load created, under Last load on the Load tab
Everything the source org holds, in one go Forge, the ALL depth Remove the records this run created, under Recent runs
Nothing left: the objects you pick, or the whole org DataOps → Cleanup, Empty Undo, on its results, while the recycle bin holds them

Seed's CSV Upload and Clone from Org are taken back as a seed is, from their results or Earlier seeds: the FAQ says what each module can undo.


Rewind an org to a checkpoint

Before a test session, a demo or a training, take a checkpoint of the org; afterwards, Rewind returns its data to that moment, whoever changed it since — you, your testers, flows or integrations — when the user SandForge connects as has View All Data and Modify All Data.

  1. Open Checkpoints, third in the launcher's Modules list, pick the org, then Take a checkpoint: Everything people work in, or Only the objects I pick. Before it runs says what the take costs; it keeps the records' values on this machine, unencrypted, readable by you alone, for 30 days unless you tick Keep until I delete it.
  2. Work in the org: create, change and delete records, in Salesforce or with any tool.
  3. Rewind…, on the checkpoint's row or on Home, opens the preview, which reads the org and writes nothing: what a rewind deletes, gives back and brings back, who last changed it, what the org runs as the rewind writes, and what neither a rewind nor its undo can take back. Where the org delivers every email, or would not say, it also names what may send one and where it goes, and Rewind waits for a box of its own.
  4. Rewind <org>…, then type the org's alias, or, for an org that has none, its name or Organization Id: the records created since are deleted, the records changed since get their values back field by field, and the records deleted since come back from the recycle bin with their Ids, or, once it no longer holds them and you accept it, are made again with new Ids. The org is read again, and what still differs is named, with why. Untick an object in the preview to rewind the others alone: what would come back only with it is left and named, with the object to add.
  5. Undo this rewind, offered on the org's last rewind for 15 days, returns the org to how it was before the rewind and keeps what anyone changed since. What the rewind deleted comes back while the recycle bin holds it, and the preview names first what Undo could not bring back.

Checkpoints — an org's checkpoints, one about to expire, one kept until deleted, and a rewind that can still be undone

Rewind preview — what a rewind would delete, give back and bring back, object by object, who last changed it, what it cannot undo, and its cost before anything is written

A run can keep its own way back: tick Checkpoint first before a Forge, Sync, Seed, Autopilot or Frozen Dataset run, and it takes a checkpoint of the objects it writes, and of those the target's flows create under them, before its first write. Rewind to before this run…, on its results, opens the preview of the rewind to it.

An org several people rewind -- a team's sandbox, a training org -- can be rewound from a teammate's machine too: Export… on a checkpoint's row saves it to a file encrypted under a key shown once and kept nowhere, and Import… keeps it on the other machine once the org answers that it is the file's and that the user there sees all data. The lock against two rewinds at once is per machine: agree on who rewinds.

Checkpoints never takes a checkpoint of a production org nor rewinds one, with no setting or flag to lift it. With View All Data and Modify All Data, a rewind puts back what anyone changed; a user without them is held to the objects they have View All and Modify All on, and what other users deleted since stays in the recycle bin, named. It rewinds data, the files attached to the records it holds among them, not metadata, users or the content of files: the guide says what a rewind leaves as it is. From the sandforge npm package or a checkout of this repository, sandforge checkpoint takes, previews, rewinds and undoes the same way without the editor: between two test suites on a CI scratch org, say. An AI agent reaches the same commands, with Seed, Forge's record clone, the removal of a run and the plan, apply and destroy of the environments a sandforge.yaml declares, as the tools of an MCP server, started by npx -y sandforge mcp or from a checkout, each write confirmed by the org's alias; the extension itself gives the model no tool.


Test data as code, for the command line & CI

A sandforge.yaml committed with your project says what records its tests need -- so many accounts, so many contacts under each, records cloned from an org it names, a Frozen Dataset it loads, or the records a sandbox copied from production already holds, masked -- and the sandforge env command, run from the sandforge npm package or a checkout of this repository, applies it to a scratch org, a Developer Edition or a sandbox the file lists by its Organization Id: plan says what it would create, keep, replace and take back, apply writes it through Seed, Forge, Frozen Dataset and DataOps and, applied again, writes nothing, and destroy takes it back into the recycle bin, but never unmasks what it masked. A production org is refused before anything is read. The guide has the file, a session of every command, and the pattern for a pipeline. Where the target delivers the emails of what still runs, or would not say, a script writes nothing without --accept-emails, which --accept-automation never stands for; the CI examples carry the switch.

In the editor, with Red Hat's YAML extension installed beside SandForge, VS Code checks a sandforge.yaml or a sandforge.yml as you type it, against the schema SandForge ships, generated from the one sandforge env validate reads the file with: a key it does not know, a kind it does not have or a value of the wrong type is underlined, the keys each object takes are offered, and hovering a key says, in English, what it holds, its default and what it refuses. The YAML extension is what reads that schema; without it, the editor checks nothing. It checks the file's shape alone: validate checks the rest, offline -- each resource against its module's own rules, the order of the resources, the variables the file names.


Screenshots

Launcher — the SandForge mark, the current org, the modules a first run needs and the others folded under Advanced, in the VS Code sidebar

Forge results — the records a run created, their ids in the target, its emails and phone numbers neutralized, and the actions to verify or remove what it wrote

Home — orgs, health, the forge entry point and the last checkpoint, ready to rewind

Sync — source and target orgs, emails and phone numbers neutralized by default, and a filtered object set

Monitor — health score, governor limits and storage breakdown

DataOps — snapshots of the objects the anonymization templates mask, with per-object results


FAQ

  • Does my data leave my machine? Only to the orgs you connect, until you turn the AI Assistant on (it is off by default) and store your own key, which stays in VS Code Secret Storage. From then on, its features send what they need to Anthropic, and a failed run's error message goes too, unless sandforge.ai.errorResolution is off; the FAQ lists what each feature sends. Diagnostics (sandforge.telemetry) is off by default and, turned on, only writes error reports to a local log. What the tools of the MCP server a checkout runs for an AI agent answer goes to that agent's model, whatever these settings say.
  • Can I point it at production? To read, yes, except with Checkpoints: it refuses a production org outright, even to take a checkpoint or preview a rewind, which only read. Forge and a Frozen Dataset load never write to one: they refuse a production target outright. The writes of Seed, Sync, Autopilot and DataOps go through the Production Guard: a confirmation before each, and destructive operations (DELETE) are blocked outright.
  • Is this an SFDMU replacement? For moving data between orgs from your editor, yes — and without the config file: you paste a record ID, SandForge discovers the relationship graph and remaps IDs on write (a record type the target does not have keeps its source Id, and the SandForge log names it). SFDMU keeps the edge for headless CI, where it is a binary you install: SandForge's thirteen command-line scripts run with npx sandforge, from the npm package, or from a checkout of this repository. Your export.json comes with you: the Migration module imports it into a Sync config, non-destructively — nothing is written to your orgs — and names what Sync will not do as SFDMU would.
  • Which orgs are supported? Any org authenticated in the Salesforce CLI (sf), imported in one click.
  • Is it free? Yes — MIT licensed, no account, no paid tier.
  • Can I undo a run? Forge, Seed (its templates, its wizard, CSV Upload and Clone from Org), Sync and Frozen Dataset each take back what a run created; Autopilot cannot, but a checkpoint taken before any run, on a sandbox, a scratch org or a Developer Edition, rewinds the org to it. Checkpoint first takes one as the run starts. The FAQ has the table.

Documentation

Guide Description
Getting Started Install, connect your org, run your first operation
Forge: Dev Sandbox Quickstart Clone a record graph from a partial-copy sandbox into your dev sandbox, in a few steps
Forge: Reference Every check, decision and file a Forge run reads, writes and keeps, and every flag of its command line
Forge: Record-Scoped Architecture Internals of the scoped clone pipeline (BFS discovery, RecordType mapping, cycle 2-pass, orphan parent expansion)
Frozen Dataset Replayable reference datasets
Seed Built-in templates for an empty org, generated data of your own, CSV import, org-to-org copy
Autopilot Whole objects from one org into another, in dependency order, optionally masked
Sync Org-to-org data synchronization with field mapping and conflict resolution
Checkpoint & Rewind Take a checkpoint of an org's data, preview a rewind to it, rewind the org whoever changed it since (with View All Data and Modify All Data), and undo the rewind; what a rewind leaves as it is
Monitor Org health, API limits, and job tracking
Compare Metadata diff, permission set and profile presence, and five Organization settings
DataOps A snapshot before anonymization and its restore, data subject requests, cleanup and a data-quality scan
Automation Visual pipeline builder: backups, comparisons, checks, notifications, by hand, on a schedule or on a sandbox refresh
AI Assistant Chat, NL2SOQL, pipeline drafts, Seed's AI rules and error resolution, and what works with AI off
Migration An SFDMU export.json imported into a Sync configuration, run from Sync
Reports Run reports, success rates, the audit trail and the data lineage of SandForge's runs
Grappe Partition-by-partition progress of large Seed and Sync runs
Command line & CI Thirteen scripts, from the sandforge npm package or a checkout: seed an org from a template, clone a record or whole tables and take the run back, clean up what a user created, empty objects or a whole org and undo it, sync, back up and restore, mask, replay a Frozen Dataset, run Autopilot, compare, monitor, take a checkpoint of an org, preview a rewind to it, rewind the org and undo the rewind, apply a sandforge.yaml to an org and take it back; and four CI pipelines
FAQ & Troubleshooting Common questions and solutions to frequent issues

Requirements

Requirement Version
Visual Studio Code 1.95+
Salesforce CLI (sf) Latest
AI API key (optional) Anthropic (Claude)

The command-line scripts need neither VS Code nor the extension. The sandforge npm package runs them with Node.js 20.19 or later and no checkout -- npx sandforge --help, and claude mcp add sandforge -- npx -y sandforge mcp for the MCP server; from a checkout of this repository they run with Node.js 24 and pnpm 11, once pnpm install and pnpm build:shared have run.


Installation

From Marketplace (recommended)

  1. Open VSCode
  2. Go to Extensions (Ctrl+Shift+X)
  3. Search for SandForge
  4. Click Install

From VSIX

Download sandforge.vsix from the Releases page, then run Extensions: Install from VSIX... from the Command Palette.


Keyboard Shortcuts

Shortcut Action
Ctrl+Shift+R Open Grappe (partition progress)
Ctrl+Shift+A Open Automation

In-app, press Ctrl+K for the command palette and G + a letter to jump between modules (see the Help page for the full map). On macOS, use Cmd instead of Ctrl.


Configuration

Setting Description Default
sandforge.showWhatsNew Show what a new minor version brings the first time a SandForge panel opens after an upgrade. A patch version never shows it. true
sandforge.telemetry Record extension errors locally for diagnosis. Nothing is sent over the network. false
sandforge.orgs.validateOnStartup Validate registered orgs when SandForge first opens a view in a window, and auto-refresh expired sessions via the sf CLI true
sandforge.forge.graphView Forge's discovery, Review and execution screens: auto shows a table past 25 objects or under 560 pixels wide, a graph otherwise; graph or table always auto
sandforge.forge.maxRecordsPerObject Most records of one object a Forge clone reads: a clone of whole tables reads and writes them a page at a time; past it, truncated 50000
sandforge.seed.defaultBatchSize Default batch size for Seed data operations 200
sandforge.sync.defaultBatchSize Default batch size for Sync data operations 200
sandforge.sync.maxConcurrentOps Maximum concurrent sync operations 3
sandforge.sync.maxRecordsPerObject Most records of one object a sync reads, from either org, 50,000 at most; past it, the run says it read the object in part 50000
sandforge.ai.enabled Enable the AI Assistant (requires an API key) false
sandforge.ai.provider AI provider (only anthropic is implemented) anthropic
sandforge.ai.model AI model used by every AI feature (chat, NL2SOQL, pipeline drafts, error resolution, Seed) claude-sonnet-5
sandforge.ai.errorResolution Send a failed run's error message to the model for a fix suggestion (Salesforce Ids removed first) true
sandforge.ai.tokenBudgetMaxPerSession Maximum AI tokens per window session, shared by all AI features (warns at 80%) 200000
sandforge.backup.maxCount Maximum number of backups retained per org 10
sandforge.backup.maxAgeDays Days a DataOps backup, which holds records' values unencrypted, is kept before it is deleted; 0 keeps it until deleted by hand 30
sandforge.backup.maxRecordsPerObject Most records of each object a DataOps backup reads; an object holding more is backed up in part, and the backup says so 50000
sandforge.checkpoint.beforeRunKeepDays Days a checkpoint a run takes before its first write (Checkpoint first), which holds records' values unencrypted, is kept; 0 keeps it until deleted by hand 7
sandforge.pipeline.timeout Pipeline execution timeout (ms) 300000
sandforge.safety.requireProdConfirmation No longer used: every write to a production org asks first true
sandforge.safety.auditLogging Record each Production Guard decision with the run it concerns in the audit trail true
sandforge.safety.confirmAboveRecords Ask before a Forge clone, an Autopilot run or a Sync writes more than this many records (0: never); one near the target org's data storage is asked about too 2000
sandforge.grappe.enabled Report large Seed and Sync runs partition by partition (an Autopilot run reports only its start and end); execution stays sequential false
sandforge.grappe.autoActivateThreshold Record count at or above which that partitioned reporting starts 10000
sandforge.grappe.grappeSize Records per grappe partition 5000

See the full list of settings in the VSCode Settings UI under "SandForge".


Internationalization

Full UI in 6 languages: English, French, German, Spanish, Japanese, Brazilian Portuguese. Key parity across locales is enforced in CI, and your language choice persists across sessions. Numbers and dates are formatted with Intl APIs in the language picked in SandForge, keeping the editor's regional conventions when the editor uses that same language. Durations are not: they are composed from fixed h/min/s/ms tokens and read the same in every locale.


Support

  • Website and guides: sandforge.fr
  • Report an issue
  • Ask a question (Q&A)
  • Changelog
  • Security policy

Missing a feature? Open a feature request — responses are fast.


Author

Stephane Berthoz

License

MIT

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft