Bone3 Skeletal AnimationBone3 Skeletal Animationbone3.com
中
Choose an article

Basic Editing

Project Names, Local Saving, Cloud Restore, and Copies

Build a reliable saving and experimentation workflow using local projects, cloud saving, and independent copies.

BeginnerAbout 12 minFor Editor v1.0 · Tutorial updated Oct 26, 2026
Download the sample PSD

After this article

Create recoverable checkpoints for exercises without treating browser storage as your only backup.

01

Name the project and save a local snapshot

  1. 1

    Change the project name

    Double-click the project name above the hierarchy and enter a recognizable name such as “PSD Documentation Practice”. Some export file names also use the project name.

    Expected resultThe project name is updated in the hierarchy and workspace.

    Double-click the displayed project name to rename it. This image locates the name rather than showing a completed rename.
  2. 2

    Save locally

    Click Save in the top toolbar and wait for the local-save confirmation. The editor also autosaves, but a manual save makes milestones easier to confirm.

    Expected resultThe local snapshot can be reopened in the same browser after a refresh.

    Click Save and wait for confirmation. Local saving uses IndexedDB and is not an upload to the cloud.
  3. 3

    Use undo rather than refreshing to fix mistakes

    Press Ctrl + Z to undo, or Ctrl + Y / Ctrl + Shift + Z to redo. Do not clear the project or site data just to undo one step.

    Expected resultThe intended state is restored without losing the rest of the editing session.

02

Use cloud saving for other devices

  1. 1

    Click Save to Cloud

    Anonymous use requires sign-in first. After signing in, the editor checks your plan's cloud-storage permission, project document, and media sizes.

    Expected resultAnonymous users see a sign-in prompt; actual cloud checks happen after signing in.

    This confirms the anonymous sign-in requirement. Sign in and check the actual cloud dialog for plan permissions and available space.
  2. 2

    Confirm and wait for completion

    Confirm the save and wait for the document and media uploads to finish. Do not close the page before success is reported.

    Expected resultCloud saving succeeds and the project appears in the workspace.

  3. 3

    Open the project on another device

    Sign in to the same account and open the project from the workspace. The editor compares local and cloud data and downloads documents and media as needed.

    Expected resultBones, images, and animations are restored, not just the project name.

03

Use copies for high-risk experiments

  1. 1

    Sign in and duplicate from the workspace

    Save, sign in, and return to the workspace. Choose “Duplicate as New” in the project actions and give the copy a test-specific name. Anonymous workspace access redirects to sign-in; no duplicate action is available there.

    Expected resultAn independent copy is created so later edits do not affect the original.

    After signing in, open the workspace and choose “Duplicate as New”. This image only demonstrates the sign-in requirement.
  2. 2

    Give each copy one experimental variable

    Change only one factor, such as automatic-weight radius or PSD orientation. Record the difference and compare the same animation segment.

    Expected resultYou can identify which change produced each result.