Reference and license records are easiest to retrieve when they are stored beside the project decisions they support. A browser history or download folder rarely provides a dependable long-term record. Keep source identity, relevant terms, and the reason a resource mattered together, distinguishing research material from assets incorporated directly into the finished illustration.
Record identity and use while the source is available
For important references, save the source URL, creator or organization where known, access date, and a short note about the information used. A machinery reference might clarify a hinge, while a historical source establishes clothing context. These notes help future revisions assess whether the same source remains relevant rather than treating every collected image as a general visual authority.
For incorporated assets, preserve the applicable license or written permission, purchase record where relevant, and required credit. Identify the exact asset and version, not merely the website that hosted it. Conditions can differ among products and licenses from the same marketplace. A folder containing the image without its terms does not explain whether it can be redistributed, modified, or used in a new context.
Separate reference-only material from files intended for the delivery package. This reduces accidental redistribution and makes the project's actual dependencies clearer. A photograph used to understand a hand position has a different role from a photograph embedded in the artwork. Record the role accurately instead of applying the same vague asset label to every external file in the research folder.
Build a retrieval path that survives project closure
Use a compact resource log or descriptive filenames that connect files with their records. Include where the resource appears in the source if that is not obvious. A texture named paper03 may be difficult to identify after several years, while a note linking it to the background group and license record makes later replacement or permission review much easier.
Store permitted local copies of relevant records where useful, because online pages can change or disappear. Follow the source's conditions and the project's storage policy rather than assuming every page or resource can be freely redistributed. Keep confidential permissions in the appropriate restricted location. The archive should preserve necessary evidence without exposing unrelated personal or commercial information to every recipient.
Before a new use or later revision, review the records against the proposed context. An old license may not cover a new client, distribution method, or editable-source handoff. Do not assume that because an asset was valid in one project it is available for every future purpose. Raise specific uncertainties through the appropriate permission or legal process before reuse becomes embedded in production.
At close, check that significant incorporated resources have identifiable records and that the archive can locate them without your browser session. Keep the system simple enough to maintain during work. Good records support accurate revisions, attribution, and responsible reuse, allowing future editors to distinguish known permission from an attractive file whose origin and allowed uses were lost in a temporary folder.