Textile Resource Access & Subscription Check

Need a current named-platform view first? Open the textile platform access map, then use this worksheet for the route and role you are actually considering.

Start with the job, not the platform

A resource can be free to browse but paid to download, free for one role but paid for another, or free at a small scale while bulk access is commercial. A monthly-looking price can be billed annually. A downgrade can leave the account intact while hiding files or removing workflow features. A directory can be genuinely useful while still using paid placement, member benefits, marketplace fees, or user-contributed records.

Write the job as an observable outcome:

• find a pattern with a specific size range and file format;
• download a weaving draft in a format your software can use;
• recruit and manage one pattern test;
• identify production locations and export a working dataset;
• create a supplier profile and understand what affects its visibility; or
• save project, stash, fabric, or pattern records and retrieve them later.

“Explore the platform” is too vague. If the job is not fixed, a feature list will make every plan look more useful than it is.

Use one access ladder

Classify the route by the deepest level needed for the job:

1. Open browse: useful records can be viewed without an account.
2. Free account: the job works after registration without payment.
3. Free plus paid: a free route exists, but named workflow, storage, volume, or convenience features require payment.
4. One-off payment or credits: the job is purchased individually instead of renewing automatically.
5. Recurring subscription: access renews monthly or annually until canceled.
6. Quote or demo: cost or access is not fully available without contacting the provider.

A platform can occupy more than one level. Record the level for the exact job, role, and volume rather than assigning one permanent label to the whole service.

Working template · local to this page

Textile resource access and subscription check

Complete one record for one platform, one user role, and one exact job. Use current first-party pages, test the signed-out and signed-in boundaries yourself, and mark anything you cannot verify as unresolved.

Print / Save as PDFCopy to clipboardClear worksheet

Your entries stay in this browser and are never sent to the server.

Anonymous action counts may be recorded. Entries, field labels, and exported records are never included.

01

Job and decision boundary

Define success before reading the pricing page.

Platform or resource and current URLExact job to completeUser role, craft or business context, and expected frequencyRequired output, format, quantity, and deadlineDecision owner and maximum acceptable commitment

02

Before account or payment

Test from a signed-out browser and record the useful boundary, not just the landing-page promise.

What can be searched, viewed, filtered, or downloaded while signed outWhat stops at registrationWhat stops at paymentAccess ladder for this jobTest date, browser state, and evidence retained

03

Account and data boundary

Registration has a cost even when no money changes hands.

Required identity, profile, organization, payment, or social-login dataContent or records you would contributeVisibility and audience of contributed informationExport, download, portability, and deletion routesPrivacy, terms, and data-use pages checked

04

Plan, price, billing, and renewal

Separate the displayed rate from the charge and commitment.

Plan name and exact features needed for the jobCurrency, taxes, unit price, and total chargeBilling interval, minimum commitment, and renewal ruleTrial, discount, credit expiry, usage cap, and overagePrice and terms checked on

05

Cancellation, downgrade, and exit

A clear exit is part of the product, not an afterthought.

Where and how cancellation is completedWhen cancellation takes effect and whether access continuesRefund, pause, downgrade, and reactivation termsWhat remains visible, usable, downloadable, or deleted after downgradeExit test or support question still required

06

Coverage, provenance, and maintenance

Access does not establish completeness or accuracy.

What population, records, regions, crafts, or production stages are coveredWho creates and edits the recordsDates, provenance, corrections, and inactive-record handlingWhat must be verified at the original sourceKnown coverage or evidence limitations

07

Commercial incentives and discovery

Record how the platform is funded and what can change visibility.

Observed business modelPaid features that affect reach, ranking, badges, files, or contact volumeNon-payment factors that affect ranking or matchingPlatform claim versus independently verified factConflict, material connection, or placement disclosure needed

08

Decision and recheck

Make the smallest reversible commitment that completes the job.

The exact job works at the recorded access levelTested with the intended output, role, and volumeThe full charge, renewal, cancellation, and downgrade effects are understoodNo decision rests on a monthly-equivalent number aloneRequired records can be retained or exported before exitAny missing portability is accepted explicitlyCommercial incentives and evidence limits are acceptableVisibility and coverage claims are not mistaken for independent qualificationDecision, chosen access level, and reasonRecheck date and triggers

What current platforms show

The point of these examples is not to rank the platforms. It is to show why one “free or paid” field is inadequate.

Handweaving.net currently separates open archive and drawdown access from subscriber-only draft files and browser tools. Its subscription page also describes recurring renewal, cancellation at the next renewal, continued access until then, and its refund position. The useful question is whether your job stops at viewing a drawdown or requires WIF download and editing.

Yarnpond splits access by role and unit of work. Its current pricing page says testers can use the service without charge, while designers can pay per test or job or use a subscription. That is not one platform-wide price. The record must name whether you are testing, publishing a test, posting a job, or maintaining another role-specific workflow.

Threadloop offers a free account and paid workflow features. Its pricing page identifies features such as project collections, PDF pattern storage, saved searches, imports, and bulk editing as paid, while its terms state that the free plan does not require a card, cancellation keeps paid access through the current billing cycle, and the account returns to free features afterward. Check which saved work remains usable for your job rather than equating “account remains” with “nothing changes.”

Open Supply Hub uses a different boundary. Its current solutions page says a free account supports search, contribution, profile viewing, and a bounded download, while paid products provide larger-scale downloads, continuous API use, or embedded maps. The paid value is operational scale, not simply permission to see records.

Common Objective combines free profiles and limited connection activity with paid content, training, sourcing, and visibility capabilities. Its how-it-works page discloses factors that affect profile ranking, while its pricing page describes cancellation by downgrade and what happens to additional portfolio items. A supplier evaluating discovery should record both access and the factors that influence visibility.

Ravelry describes a user-driven pattern and yarn database, personal notebook, directories, and community on its official site overview. Community scale and record richness are useful properties, but they do not convert every record into independent verification. Record who maintains consequential information and what must be checked with the designer, yarn company, shop, or other original source.

Stop conditions

Do not pay or contribute important records when the exact job cannot be tested or explained; the charge or billing interval is unclear; renewal or cancellation terms cannot be found; downgrade effects are material but unknown; required files cannot be exported; a promotion is the only visible price source; the platform's own records conflict; paid placement or ranking inputs are material but undisclosed; or the decision depends on a provider, certificate, price, stock, fit, or availability claim that has not been checked at its responsible source.

Sources and decision boundaries

• Handweaving.net subscription publishes its current free and paid feature boundary plus renewal and cancellation terms.
• Yarnpond pricing publishes role-specific free, one-off, credit, and subscription routes.
• Threadloop pricing and terms publish the current paid-feature and cancellation boundary.
• Open Supply Hub solutions distinguishes free search and bounded download access from paid operational-scale products.
• Common Objective how it works and pricing describe free and paid capabilities, visibility inputs, downgrade, and retained portfolio limits.
• Ravelry about describes the scope and community-maintained nature of its pattern, yarn, notebook, and directory records.

These are current first-party descriptions checked on July 28, 2026. They establish examples and a repeatable comparison structure. They do not prove that every feature works as described for every account, preserve historical terms, compare service quality, or independently validate provider claims.

FAQ