Create, save, and export scripts

Write a motion script from scratch or export an edited version. Learn how edits are saved and when to export a copy or sync changes to the original file.

Before you start

You can create a script without generating one from video first. Save the version before exporting. Sync funscript is available only for tracks with an imported source file.

01 Start with a blank script

  1. In Library, click New script, or choose New script from Studio's Editor entry.
  2. A new script starts with no nodes. Open Duration and set its timeline length; this example uses 15 seconds.
  3. Turn on Add node and place alternating high and low positions in the waveform. Press Esc to finish. Select nodes to adjust their position or time. Start with a few nodes to check the rhythm.
  4. Click Save and enter a Title. Description is optional. This example uses Four-beat practice.
  5. Click Save script and check Saved and the version information. The new script appears in Library → Scripts. Saving does not automatically link it to a video.
  6. To use it with a video, follow Match and link scripts. Use Export when you need a file.
You can add nodes to a blank script without generating a script from video first.
A new 15-second script with four nodes
A new script needs a title on its first save. Later edits to the active track save automatically.
Saving a new script with the title Four-beat practice and a description

02 Save and export a script

Current stateWhat to do next
Normalize / Clamp / Smooth / Scale / Phase Shift / Repeat previewApply commits the edit; Cancel or Esc discards it. A preview is not a saved version.
Edits applied to the active trackStop editing and wait for Saved. Unsaved means saving is still in progress. Follow any error or conflict message.
New script or metadata changesCheck Title and Description, then click Save script.
A copy opened from HistoryApply version to commit the edited copy. Comparing a version does not apply it.
  1. Finish transform previews, resolve unapplied session copies on each axis, and confirm the versions you want.
  2. Click Export, choose a destination, and wait for Script exported.
  3. Check the exported .funscript and any additional axis files. Reimport them if you want to verify the result.
The exported file contains four nodes. Reopen the saved script in Library to keep editing.
Four-node script exported successfully, with the destination path hidden

Use Library → Import → Import script to reopen the main .funscript. If export fails, use Retry export or choose a writable destination.

How do Export, Sync funscript, and backup differ?

Export saves the stored tracks and metadata to files. Sync funscript lists the local source files it will replace and asks you to confirm. It does not create a separate backup. Settings → Library → Back up… backs up the library. A track without an imported source shows No source file.

03 Verify multi-axis files and sync sources

This example uses a script with L0 and R0 tracks. Check every axis file. ZIP export bundles the scripts and metadata together; the primary-axis file alone does not contain every axis.

The export contains a main file and .twist.funscript, with 42 L0 nodes and 41 R0 nodes, plus a .peaksync.json metadata file. Keep the shared filename prefix and axis suffixes. Select the main file when reimporting, then check both tracks. For ZIP exports, extract the archive first.

After export completes, check the primary axis, additional axes, and metadata on disk.
Successful L0 and R0 export, with personal paths hidden
Reimporting preserves all 42 L0 nodes and 41 R0 nodes, matching the exported files.
Reimported script with L0 and R0 intact and 42 nodes on L0
  1. Save the versions you want for each axis. Resolve any Session only copies with Apply version first.
  2. Click Sync funscript and review the axes, versions, and source files in Replace these local source files?
  3. Confirm that these are the imported files you want to update, then click Sync files. To keep the original files, cancel and use Export to save elsewhere.
  4. Tracks without imported sources show No source file. New or generated scripts cannot sync to a source file that does not exist.
  5. If Source sync pending appears, use Resume sync as directed. For errors, check file availability and permissions before retrying.
  6. Reopen the source files after syncing and verify the edited nodes.

Here, the first L0 node in the reimported script changes from 50 to 60. After Saved appears, sync the files. On completion, Source files synced appears. The source file now starts at position 60; node times and all 41 R0 nodes are unchanged.

Before syncing, check the axes, versions, and source files to be replaced.
Sync confirmation listing L0 v2, R0 v1, and masked source paths
After the app confirms completion, check the nodes in the actual source files.
Source files synced, with the first node at position 60

To back up the library, open Settings → Library → Back up…. For the full workflow, see Library backup. Export, sync, and library backup preserve different things.

Check your changes

The intended versions are saved. Reimporting preserves axes and nodes, and syncing updates the actual source files.