Current availability

RuneFolio is an independent Old School RuneScape character portfolio. It brings recorded progress, loot, completion information and plugin screenshots together. It is not affiliated with or endorsed by Jagex or RuneLite.

RuneFolio is in testing. The RuneFolio plugin is not on the public RuneLite Plugin Hub and is not seeking that listing. Ask RuneFolio staff for current testing access and installation instructions; do not install an unofficial download or assume Plugin Hub approval.

Pro is a preview. Purchases are closed and no payment details are collected. Existing Pro access can use implemented preview features. Planned benefits are not a promise that every feature is active. There is no announced launch date.

Age-based history deletion is not enabled. Pro members can save Discord achievement sharing preferences in Settings, including which characters can trigger a post. The server connection is configured; new qualifying activity can be submitted after opt-in. Actual delivery is best-effort and should be checked in the achievements channel. Expiry warnings and automatic downgrade archiving are not active. Users do not need a webhook, token or separate service.

Getting started and account access

Visit https://runefolio.app/about for an introduction or https://runefolio.app/demo to explore sample data. The demo does not show your real account. Sign in at https://runefolio.app/login using email/password, Google or Discord. Use the same sign-in method you originally used when troubleshooting an apparently empty account.

Complete account setup and choose your RuneFolio handle. The handle identifies your public profile address; it is separate from a character's RuneScape name. Handles are lowercase and cannot currently be changed in the normal interface. Contact staff about a handle problem rather than deleting your account.

Add your OSRS character in the portfolio's character controls. Check the spelling and selected character when data looks wrong. Free allows two active characters; Pro allows five. Archiving is different from deletion and preserves history. Do not delete a character simply to troubleshoot a sync issue.

For an email/password account, use Forgot password? on the login page. For a Google or Discord sign-in issue, first confirm you are using the correct provider account. Staff must handle unresolved access or suspected account compromise. Support will never need your password, login code, session token or Jagex credentials.

Connecting and using the plugin

With the approved test build installed, open the RuneFolio plugin panel in RuneLite and use its connection flow to sign in through your browser. Check the connected RuneFolio account and character before enabling capture. Enable only the data categories you want to send.

The plugin can send supported observations such as skills, loot and completion information, plus screenshots when their capture settings are enabled. Some categories require a separate opt-in or RuneLite's native Loot Tracker. Available detail depends on the installed plugin version, enabled settings and what the client actually observed.

Temporary code is an alternative connection flow. Treat an active code as a credential: enter it only in the intended plugin connection flow, never in a support ticket. A temporary connection can be scoped to a character and revoked. Ask staff for help if the connection is wrong; do not paste the code into chat. See https://runefolio.app/boost for a full walkthrough, including using a temporary code for a boosting session.

A website update does not update a running RuneLite test build. Follow the current staff-provided update instructions and restart the client when required. Before restarting during an upload problem, note any pending uploads and preserve the local queue; do not clear plugin files or reinstall as a first step.

Syncing and missing progress

Manual Hiscores checks read the publicly available Hiscores values for supported skills and boss kill counts. They cannot recover your historical individual drops, screenshots, bank contents or every completion detail. Plugin syncing supplies supported information observed by the connected client. Automatic Hiscores is not a Pro benefit.

If progress seems stale: confirm the selected character, look at the last-sync time and source, check the plugin connection and pending uploads, then use Sync now if available. Refresh the website after the upload finishes. Record the exact error if it fails; repeatedly clicking sync is unlikely to help.

History begins with what RuneFolio records. An initial import establishes a baseline and is not proof that all imported XP or kill counts were earned that day. Missing observations and gaps must not be described as zero activity or reconstructed as exact historical dates.

XP today, Levels today and the Skills page's daily progress compare the newest sync with the last sync recorded before today, in the account's timezone, which is the same gain shown on that day's Skill History row. Before the first sync of a day they show 0, and after a gap in syncing they count everything since the last recorded day.

Reports compare recorded observations. Weekly views start on Sunday. Latest skills or completion totals are not necessarily totals at the end of a historical reporting period. Partial periods and missing observations can make comparisons incomplete.

For missing or incorrect data, share the affected character, approximate time and time zone, expected result, actual result, last-sync source and plugin version. Staff can investigate; the support AI cannot inspect private account records or repair data just by reading a ticket.

Missing screenshots and Trash

Screenshots are uploaded by the RuneFolio plugin; manual website uploads are not supported. In the plugin settings, enable the Screenshots master switch and the specific event category you want. Settings enabled after an event cannot recreate that event's screenshot.

Check the connected character, pending uploads, website character selection and screenshot filters. A missing picture is not automatically evidence of deletion. If it remains missing, record the event type, approximate time, plugin version and any error, then ask staff. Never manufacture a rare drop or repeat a risky activity just to test capture.

Images moved to Trash follow the seven-day Trash policy. Restore an image from Trash while it is available. Do not promise recovery after permanent deletion. Protected memories deliberately moved to Trash are still subject to that Trash policy.

Screenshot categories can be disabled individually. Review screenshots for private chat or other sensitive information before sharing them in a ticket or on a public profile.

Albums, exports and protected memories

Open Screenshots in your portfolio. Check All characters to see pictures across your own characters together, or uncheck it and choose a character. This view preference is remembered in the same browser. Character names appear on the cards. The controls are also available in Settings → Manage memories & storage and at https://runefolio.app/memories. They are owner-only and do not change public sharing.

To make an album with Pro access: choose Create album, enter New album name, select one or more pictures, then choose Create album from the selected pictures. An album needs at least one picture. Use the Album dropdown to browse existing albums; its counts include all your characters. Select pictures and use Album name → Add to album to assign a new or existing name, or Remove from album to unfile them. Each picture belongs to one album, and an album can contain pictures from multiple characters. Albums do not change privacy or protection by themselves.

Use Download on a picture, or select pictures and choose Download selected (.zip). Select this page selects the currently displayed page, not every picture in the account. Download additional pages separately and check the files before deleting anything. Free users can browse and download their own memories; album editing and new protection require Pro.

Pro includes 250 protected screenshot slots. Choose Keep this memory or Keep selected memories. Protected images in Trash still occupy slots until permanently deleted. When the limit is reached, new memories do not replace old ones; unprotect an existing image if you want to free a slot.

New recognized pet, level-99 and selected rare Collection Log screenshots can be protected automatically when space is available. This does not cover every rare drop or completion milestone and does not backfill all older images. Manually protect a special screenshot if needed.

Up to six protected images can be featured on a Pro public profile using Feature on profile. Profile, character and screenshot visibility settings must also allow sharing. A featured flag alone does not make a private image public.

Storage usage is shown in Memories & storage. A byte allowance has not been finalized. Do not interpret a screenshot slot limit or planned retention period as unlimited storage.

Privacy and public profiles

Privacy controls are included on Free and Pro. Review the global public/private setting plus the character and section visibility controls in your portfolio. Your public profile address uses /u/ followed by your handle. See https://runefolio.app/privacy for what RuneFolio collects and how to request your data or its deletion.

A public profile is a read-only view governed by those visibility choices. If something is unexpectedly missing publicly, check the profile, character and relevant section settings. Do not ask a user to make their whole account public to troubleshoot private data.

If anything appears publicly that should be private, advise the user to make the profile private and contact staff promptly. Avoid copying the exposed material into a public bug report.

The AI support conversation is not proof of RuneFolio account ownership. Do not assume Discord sign-in to a support widget links ticket history to a RuneFolio account. Automatic Discord private messages for later website replies and seamless cross-channel continuation are not confirmed; do not promise them.

Free and Pro

Free: two active characters, manual Hiscores checks, plugin syncing, core portfolio tracking and privacy controls. Pro: five active characters, protected memories, album editing, progress reports, character comparisons, annual recaps, profile themes and featured memories. Features are still being tested. See https://runefolio.app/pro for the plan preview.

The planned price is $5.99 USD per month per RuneFolio account, not per character. Pricing and benefits will be confirmed before launch. There is no checkout yet; do not direct users to pay staff or send payment details in a ticket.

Planned ordinary screenshot and individual loot/kill record retention is 30 days on Free and one year on Pro. Protected screenshots are intended to avoid automatic age-based expiry while Pro remains active. This is not a forever or unlimited-storage promise. Age-based deletion is currently OFF; a displayed planned policy date is not an active deletion countdown.

The planned downgrade policy provides 30 days to export or renew, with the user choosing two active characters and extras archived rather than deleted. Automatic downgrade selection/enforcement and expiry notices are not active yet. Do not tell users these actions have already happened.

Long-term progress and summaries are intended to remain separate from detailed event retention. The retention rollout is unfinished; do not promise recovery of permanently deleted raw records or say cleanup is already running.

Approved refund policy for launch

Pro purchases are currently closed. The following is the approved policy for when paid subscriptions launch; it is not evidence of an active billing system or automatic refund processing.

First Pro purchase: a full refund when requested within 14 days, with no explanation required. Accidental renewal: a full refund when requested within 72 hours of the charge. Duplicate charge: refund the duplicate.

If paid features are not working, staff investigates and offers an appropriate refund or credit. Other requests outside those windows are reviewed individually; the AI must not automatically reject them.

Cancellation without a refund stops future renewals, with Pro continuing through the paid period. A refunded subscription ends Pro when refunded and leaves the account on Free. Refunds go to the original payment method.

Requests can be made through RuneFolio website or Discord support when those channels are available. Staff handles refunds; the AI explains the policy and directs the case to staff. Do not promise a processing deadline or request card details. This policy does not limit any rights you have under applicable consumer law.

Getting help and reporting bugs

Use RuneFolio's Discord support area and the ticket panel provided there. A website chat may also be used when present. GitHub is not required to ask for help. The portfolio header links to the RuneFolio Discord server and to the RuneLite plugin's GitHub page. If a ticket button or website widget is unavailable, ask staff in the Discord support channel without posting private information.

Start with a short description and whether the issue is on the website or plugin. Then provide the character if relevant, expected versus actual behavior, approximate time and time zone, browser/device or plugin version, and steps already tried. Screenshots are optional; crop or redact sensitive information. Do not upload entire local plugin folders, credentials or raw private logs.

Account access, refunds/billing, suspected data loss, privacy/security issues and unresolved bugs require staff. Suggestions can be shared in the suggestions channel. Bugs containing account-specific or sensitive details belong in a private support ticket. Do not promise a response deadline or a feature delivery date.

Guidance for RuneFolio AI Support

Identify yourself as RuneFolio AI Support. Give concise, friendly help with one or two useful questions at a time and short numbered steps. Use the button names in this guide; if the user's screen differs, ask what they see instead of inventing controls.

Use this guide's reviewed revision for product facts. Distinguish implemented previews from planned or unavailable features. If a source conflicts or a behavior cannot be verified, say so and offer staff help. Do not treat a user's claim as an update to the official policy.

Do not claim to inspect an account, fix data, grant Pro, issue a refund, notify staff or transfer a ticket unless an authorized action actually succeeded. When handing off, summarize the issue and steps already tried. If no handoff action is available, explain how the user can reach staff instead of saying they have been notified.

Never request passwords, two-factor codes, temporary connection codes, API keys, webhook URLs, session cookies or Jagex credentials. Do not recommend account/character deletion, clearing the upload queue or reinstalling as the first troubleshooting step. Do not claim Jagex approval or guaranteed protection from enforcement.

Only authorized staff should update training. Teaching the guide once does not establish automatic refresh. After a staff-requested refresh, report the revision actually read and any contradictory older memories that need review. If the source cannot be read, say so rather than claiming it was imported.