Skip to content

OnlineGraphing Workflow

How to Export and Reopen an OnlineGraphing Project

OnlineGraphing offers several export formats because a finished image and an editable project serve different purposes. The safest workflow is to keep an editable project file and create presentation formats only when needed.

Recommended practice: save an OGP project as the editable master, then export PNG or SVG for documents. Use HTML when a browser-openable project package is useful, but retain the OGP file as your main archive.

1. PNG: convenient raster image

PNG is suitable for:

  • Word documents and worksheets;
  • PowerPoint or Google Slides;
  • web pages that need a standard image;
  • quick sharing through messaging or email.

A PNG has a fixed pixel size. It can look sharp at its intended display size but may become soft when enlarged substantially. Before exporting, set the graph dimensions, axis range, font size, line thickness, and background exactly as you want them.

2. SVG: scalable vector output

SVG stores shapes, paths, and text as vector information. It is usually the best format when:

  • the graph will be enlarged;
  • the result will be edited in vector software;
  • fine lines and mathematical labels must remain crisp;
  • the document may be printed at different sizes.

Some office applications handle SVG better than others. If an application changes fonts or clipping, keep the SVG archive and create a PNG fallback.

3. Copy: fastest route into another application

The Copy command places a rendered result on the clipboard when the browser permits clipboard access. It is useful for a quick paste into Word, PowerPoint, an image editor, or a chat message.

If Copy does not work:

  • confirm that the browser granted clipboard permission;
  • try from a secure HTTPS page;
  • use the PNG download as a reliable alternative;
  • check whether the target program accepts image data from the clipboard.

4. OGP: editable OnlineGraphing project

An OGP file is the format to keep when you need to reopen and continue editing. It preserves project information such as graph objects, tables, annotations, inserted images, styles, axes, and other settings supported by the current project schema.

Use a descriptive file name, for example:

quadratic-variation-table-v1.ogp

Keep multiple versions before major changes. A simple naming pattern such as v1, v2, and final makes rollback easier.

5. HTML: browser-openable project package

The HTML export is useful when you want a file that opens through a browser-based launcher. It can carry the project information needed by the OnlineGraphing page to reconstruct the work. Browser security settings, moved assets, or future browser changes can affect an HTML package, so do not use it as the only backup.

For long-term editability, retain the matching OGP file alongside the HTML export.

6. Reopen an OGP project

  1. Open the appropriate OnlineGraphing tool page.
  2. Choose Open or the project-import command.
  3. Select the OGP file from your computer.
  4. Wait for all objects, images, formulas, and styles to load.
  5. Inspect the result before making new edits.

If the project was created with an older version, the loader should preserve supported IDs and settings. Still, verify custom colors, images, mathematical labels, table widths, and any feature that has changed between releases.

7. Reopen an HTML project

Open the exported HTML file in a modern browser. If the browser blocks local resources or the launcher cannot reach required site assets, open it through the website workflow or use the OGP backup. Avoid editing the HTML source unless you understand the embedded project data.

8. Insert a graph into Word or PowerPoint

  • Use PNG for the most predictable compatibility.
  • Use SVG when the application supports it and the image must scale cleanly.
  • After insertion, resize from a corner to preserve aspect ratio.
  • Do not enlarge a small PNG far beyond its exported size.
  • Keep a copy of the editable OGP project in the same folder as the document.

9. A robust file-management workflow

  1. Create or edit the project.
  2. Save an OGP master file.
  3. Export SVG for high-quality graphics.
  4. Export PNG for universal compatibility.
  5. Use HTML only when its browser-openable behavior is specifically useful.
  6. Store the files together with clear version names.
  7. Test reopening before deleting an older working copy.

10. Privacy and portability

When a project contains an inserted image or private annotation, inspect every exported format before sharing. An editable project may preserve information that is not visible in the final cropped image. Share only the format appropriate for the recipient.

Common mistakes

  • Keeping only a PNG and later expecting to edit individual graph objects.
  • Using HTML as the sole long-term backup.
  • Overwriting the only OGP file after a major edit.
  • Not testing the reopened project before distribution.
  • Sharing a project file that contains hidden or background material.
  • Assuming SVG will look identical in every office application.

Open the User Guide for current interface instructions. You can also begin a new project in the Graphing Calculator, Variation Table tool, Graph Shading tool, or Solid of Revolution visualizer.