Edit a cross-stitch chart on a phone without losing work
Use a careful mobile workflow for local photos, precise cell edits, exports and backups.
A phone is useful for trying a crop or checking a chart while you stitch. It is less forgiving when a tiny touch changes the wrong cell or a browser closes before you save. A deliberate mobile workflow keeps the project manageable: start small, separate navigation from editing, and download a backup before switching tasks.
Prepare the source outside the editor
Use the photo application's crop controls to make a copy with the intended composition. Keep the original photograph. A tight crop reduces the amount of unrelated scenery that competes for the chart's limited stitches. Avoid importing a screenshot of a photograph if the original file is available; the screenshot may add borders and discard useful source information.
Choose a modest starting width while experimenting. A 100 by 100 chart has 10,000 positions; a 200 by 200 chart has 40,000. Increasing both dimensions doubles the width and height but quadruples the cell count. The larger project can require more memory and make precise review harder on a small screen, even when the image itself fits in the viewport.
Set up a precise editing view
Turn the phone to the orientation that gives the chart and controls enough space. Zoom until you can clearly identify the target cell and at least one nearby landmark. Keep row and column references visible when possible. Do not rely on the apparent color alone when several palette entries are similar.
Before editing an important feature, try one change in an obvious area and verify what happened. Learn whether a gesture pans the page, zooms the browser or edits a cell in your particular browser and device. Touch behavior can differ across software versions. If navigation repeatedly causes accidental edits, save the project and finish the detailed cleanup on a larger screen.
Work in short, checkable passes
- Choose one area, such as the left ear or a background corner.
- Confirm the active palette color or erase mode.
- Make a small group of changes.
- Zoom out and compare the result with the overall image.
- Save a new project version before moving to another area.
A short pass is easier to check than a long series of taps with no visual review. For example, fix five unwanted background cells, then confirm the silhouette. Editing fifty cells at once makes it harder to identify where an accidental touch occurred. Keep the original conversion available as a reference.
Know where downloads go
After exporting a JSON project or PDF, open your device's files or downloads area and confirm that the file exists. A preview sheet is not always proof that a file has been saved to a location you control. Use a meaningful filename and reopen the project when practical. ThreadChart JSON is the editable backup; a preview image alone is insufficient.
Browser-local processing means the chart work happens on the device rather than requiring a photo upload to a conversion service. It also means a second device does not automatically receive your project. Transfer a file using a method you trust when moving between phone and computer, and think about where personal photographs are stored during that transfer.
For reading a chart while stitching, consider opening the exported PDF in a viewer you find comfortable rather than keeping an editing session active. DMC's chart guidance explains why the legend and symbols matter; on a small display, keeping those references accessible is particularly useful.
Finish each session by saving the editable file and noting the current revision. Local autosave helps with convenience, while explicit exports protect the work you would not want to recreate.