# Distinguish filenames, share-page URLs and media URLs for iCouldPlay

Language: en
Canonical: [Distinguish filenames, share-page URLs and media URLs for iCouldPlay](<https://allluckly.cn/en/guides/icouldplay-filename-url-character-check/>)
中文：[中文 HTML](<https://allluckly.cn/guides/icouldplay-filename-url-character-check/>)
English: [English HTML](<https://allluckly.cn/en/guides/icouldplay-filename-url-character-check/>)
Published: 2026-11-03T00:00:00+08:00
Modified: 2026-11-03T09:34:11+08:00
Author: Bison

Use a test copy containing a space and number sign to distinguish filenames, URL encoding and share-page links.

English translation of the [Chinese original](<https://allluckly.cn/guides/icouldplay-filename-url-character-check/>), translated on 2026-11-03. Original publication dates, attribution, code and version notes are retained.

A clip that opens with a simple name but fails with spaces or a number sign may have an addressing problem rather than a video-codec problem. Use controlled copies to compare directory and link access, checking identity, URL and permissions separately. Do not expose a private server or bypass login or signature restrictions. Filenames and URLs follow different rules, so similar visible characters can mean different things; avoid randomly deleting punctuation until something happens to work.

## Prepare two identical-content copies

Keep a short self-made clip under a simple reference name and copy it to a name containing a space and number sign, such as “sample 01 #A.” Change only the name, retaining extension and media bytes. Put both in one controlled folder and record duration and visual marks. Do not bulk-rename a real library whose indexing, caption matching and references may depend on names. Two disposable samples narrow the problem before any naming-policy change.

## Start with directory browsing

Open both through an existing Files or server-directory path and check matching content and duration. If they differ already, examine source naming support, listing freshness and old duplicate selection. A listed name does not prove readable content. Investigate links only after both play through a directory, preserving a known working path. If the source has no direct-link entry, stop at directory checks rather than assuming iCouldPlay accepts every manually pasted URL.

## Use the complete source-provided link

Prefer an explicit media address or existing open action supplied by the source instead of constructing a path from names. Record whether it came from a media, download or share-page entry, but keep private query parameters out of public notes. A share page with buttons may not return video; changing its extension cannot convert it into media. Note login and expiry requirements and avoid blaming a space for restricted access. Change one condition at a time rather than name, login and link together.

## Understand number-sign and percent syntax

[RFC 3986](<https://www.rfc-editor.org/rfc/rfc3986>) defines the number sign as a fragment delimiter and percent encoding as a representation of bytes; these cannot be casually exchanged with literal filename characters. A source must appropriately encode a filename’s number sign when generating its URL, but repeatedly encoding an entire generated address can also break it. A space may appear encoded in the interface. The standard explains address boundaries, not complete support by a particular server or player. Verify a source-provided address under its actual access conditions.

## Avoid whole-address substitutions

Copy the source address intact rather than globally turning encoded sequences into spaces or text. Query parameters may participate in authorization or signing, and changing one can invalidate a good file’s link. Encoding an already encoded percent sign can likewise target another name. Verify the simple-name reference and ask the source for correct generation rather than repairing complete addresses through trial and error. Keep sanitized structural examples for notes without pretending they remain usable real links.

## Compare name and access path together

Create four cells: simple-name directory, special-name directory, simple-name link and special-name link; mark absent paths not applicable. Record actual readable content, not merely connection success. Only a failing special-name link with working directory files suggests address generation or transfer, not a proven code defect. Two failing links call for link-type and access checks first. Do not change server protocols or public permissions for one failing cell; keep the experiment limited and recoverable.

## Use renaming only to test a hypothesis

If renaming the test copy back to a simple name, preserve observations, refresh the source listing or regenerate its link, and repeat the same check. An old link can still target the old path, so failure immediately after renaming is inconclusive. Neither stale caches nor one successful rename establish a universal English-only naming rule. Consider caption matching, recognition and personal search. The experiment identifies where name handling struggles rather than treating international text or punctuation as inherently wrong.

## Keep a reproduction without exposing access

Keep the naming pattern, source type, four outcomes, app version and login requirements. For support, prefer nonprivate self-made samples and a sanitized folder description rather than real addresses containing accounts, tokens or signatures. Explain that a redacted address cannot reproduce access and needs a newly generated test link. Remove only test copies, confirming originals and captions were not renamed. Next time, separate directory access from links before random character deletion or reinstallation.

## Related tutorials and sources

[Diagnose expired links](<https://allluckly.cn/en/guides/icouldplay-expired-link-versus-buffering/>), [Distinguish same-name copies](<https://allluckly.cn/en/guides/icouldplay-same-name-import-copies/>).

Checked on November 3, 2026 against the [official iCouldPlay App Store listing](<https://apps.apple.com/cn/app/id6755653178>) and [Apple public lookup](<https://itunes.apple.com/lookup?id=6755653178&country=cn>): version 1.1.1, requiring iOS / iPadOS 15.0 or later. This exercise uses the public scope of file import, network sources, playback, captions and progress. Check controls in your installed version. Self-made samples, manual records and external file preparation are workflows, not newly promised automatic features. No physical-device or private-server test is claimed.