Contact Us

    Have a question, a bug to report, or an idea for a tool FrameAnim is missing? We read every message that comes through. The form below opens your own email client with the details filled in, so you keep a copy of whatever you send us.

    We aim to reply within a few business days. FrameAnim is maintained by a small team, so a detailed message almost always gets a faster and more useful answer than a short one.

    Email

    manu.contentlab@gmail.com

    Feedback

    We value your input and use it to make FrameAnim better for everyone.

    What we can help with

    Most messages fall into one of these four buckets. Naming the one that fits in your subject line helps us route it to the right place.

    Bug reports

    Something in the editor misbehaving — a tool that stops responding, an export that comes out wrong, a project that fails to reopen. These get priority.

    Feature requests

    A tool, shortcut or export format you keep reaching for and not finding. Tell us what you were trying to make when you noticed it was missing.

    Tutorial corrections

    If a step in one of our guides is wrong, unclear, or out of date with the current editor, point us at it and we will fix the page.

    Privacy and data questions

    Questions about how your projects are stored, or requests related to your data. Your work stays in your own browser, which our privacy policy explains in full.

    Writing a bug report we can act on

    FrameAnim runs entirely in your browser, which means a bug often depends on which browser and device you are using. Reproducing a problem is usually the slowest part of fixing it, so the more of the following you can include, the sooner it gets resolved:

    • Your browser and operating system — for example "Chrome 131 on Windows 11" or "Safari on iPadOS 18". Canvas behaviour genuinely differs between them.
    • What you did, step by step — the sequence of actions leading up to the problem, starting from a new project if you can reproduce it that way.
    • What you expected versus what happened — these are often different in a way that is obvious to you and not to us.
    • Project size — roughly how many frames and layers were in the project. Several export issues only appear past a certain size.
    • An exported GIF or a screenshot — if the problem is visual, seeing it saves a long exchange of messages.

    You might find it faster here

    A lot of the questions we receive are already answered in writing. These are the pages people are usually looking for:

    • Tutorials — step-by-step guides covering timing, onion skinning, layers, walk cycles and exporting.
    • Exporting your animation — which format to pick, and what to do when an export looks wrong.
    • Privacy policy — where your projects are stored and what leaves your device.
    • About FrameAnim — what the tool is for and what it can do today.