Keep your making connected
How to sync your Ravelry stash and projects with Stashora
The quick answer
Stashora supports automatic two-way sync for supported Ravelry stash and project changes. With your account connected and automatic sync enabled, routine supported updates can sync without approving every exchange. Conflicts, possible duplicates, and other cases needing a decision are handled separately. Sync requires an internet connection and access to the sync feature.
On this page
Connecting an account and syncing are different
Connecting Ravelry opens connected features such as your library, favorites, queue, and forums. Synchronizing a stash or project exchanges supported information between the app and Ravelry; downloading a library PDF is a different operation.
Stashora can also organize local yarn and projects without a Ravelry account. Automatic sync does not imply that every local field or every Ravelry feature is mirrored. Check the records you use and the options available in your installed version.
Sources: Stashora on the App Store
Set up a connected workflow
Automatic sync handles routine changes. It is not a promise of an instant update on another service while your phone is offline, the app is inactive, or a service is unavailable.
- Connect the Ravelry account that holds the stash and projects you want to use.
- Check that your plan includes the sync feature and enable automatic sync in the app.
- Keep an internet connection available and let the app finish its current synchronization.
- Check a familiar record in Stashora and Ravelry so you understand the supported information being exchanged.
- Keep an eye on sync status. Address any conflict or other decision the app asks you to resolve.
Routine updates are automatic; exceptions need attention
You do not have to approve every ordinary supported change. Stashora separates updates it can apply automatically from cases that need a decision, such as conflicting edits, possible duplicate records, or destructive changes.
When an exception appears, check the record and the proposed outcome before choosing how to resolve it. A request for attention is different from the normal background synchronization workflow. Do not assume an error means you should recreate the item.
| Situation | What to do |
|---|---|
| Routine supported change | With automatic sync enabled and available, let the update complete; check status if it has not appeared. |
| Conflicting or ambiguous information | Resolve the decision shown by the app, based on the record you want to keep. |
| No connection | Continue with locally saved information; reconnect for Ravelry updates. |
| Sync error or paused feature | Check the reported issue, account connection, and feature access before retrying. |
Example: two different quantities for the same yarn
Suppose you changed a yarn quantity in Stashora and also edited that record on Ravelry. If the app reports a conflict, compare both values with the yarn you actually have. A recent-looking number is not necessarily the right one.
Check whether part of the yarn is reserved for another project, verify the quantity and its unit, and resolve the choice shown by the app. This is an illustration of a decision, not a promise that every Ravelry quantity field uses the same unit or mapping.
Sync, offline access, and backups do different jobs
| Capability | Purpose | Remember |
|---|---|---|
| Ravelry sync | Exchanges supported stash and project changes | Needs a connection, feature access, and enabled settings for automatic updates. |
| Local offline access | Keeps saved stash, projects, counters, and downloaded PDFs available | Does not fetch new Ravelry information. |
| A separate backup routine | Keeps a recoverable copy outside your active workflow | Two-way sync is not a historical backup. |
When an update has not appeared
Check your internet connection, connected account, automatic sync setting, and access to the sync feature. Look at the current sync status and any errors or unresolved decisions. Allow the app to finish before assuming the change failed.
If the result remains unclear, keep the record name, the edit you expected, and the displayed error. Contact support before recreating a large set of records. The existence of a local edit does not prove that a remote update has completed.
Frequently asked questions
Do I need to approve every Ravelry update?
No. With automatic sync enabled and the feature available, Stashora can apply routine supported stash and project changes automatically. Conflicts, possible duplicates, and other cases requiring a decision are handled separately.
Does Stashora synchronize every Ravelry field?
No. Sync covers supported stash and project information. Library downloads, local notes, counters, and other features are distinct workflows; do not assume every field is mirrored.
Can I sync while offline?
No. You can use locally saved information offline, but exchanging changes with Ravelry requires an internet connection. Check sync status after reconnecting.
Sources and review
Written by Stashora. Content reviewed on October 17, 2026. Worked examples and checklists are illustrative; they are not performance tests. Read our editorial policy.
